Update .NET Supported OS Matrix
dotnet/core
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
Keep the repository's linted Markdown passing npm run lint:markdown.
Install Lint Repository Markdown
$ npx skills add codsen/codsen --skill lint-repository-markdown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install codsen/codsen lint-repository-markdown --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/lint-repository-markdown .claude/skills/lint-repository-markdown && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lint-repository-markdown" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdown into .claude/skills/lint-repository-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-repository-markdown", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdownType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add codsen/codsen --skill lint-repository-markdown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install codsen/codsen lint-repository-markdown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/lint-repository-markdown .agents/skills/lint-repository-markdown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lint-repository-markdown" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdown into .agents/skills/lint-repository-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-repository-markdown", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codsen/codsen --skill lint-repository-markdown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install codsen/codsen lint-repository-markdown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/lint-repository-markdown .cursor/skills/lint-repository-markdown && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lint-repository-markdown" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdown into .cursor/skills/lint-repository-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-repository-markdown", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/codsen/codsen.git --path .agents/skills/lint-repository-markdown--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add codsen/codsen --skill lint-repository-markdown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install codsen/codsen lint-repository-markdown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/lint-repository-markdown .gemini/skills/lint-repository-markdown && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lint-repository-markdown" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdown into .gemini/skills/lint-repository-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-repository-markdown", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install codsen/codsen lint-repository-markdownInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add codsen/codsen --skill lint-repository-markdown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/lint-repository-markdown .github/skills/lint-repository-markdown && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lint-repository-markdown" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdown into .github/skills/lint-repository-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-repository-markdown", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add codsen/codsen --skill lint-repository-markdown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install codsen/codsen lint-repository-markdown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/lint-repository-markdown .opencode/skills/lint-repository-markdown && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lint-repository-markdown" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/lint-repository-markdown into .opencode/skills/lint-repository-markdown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lint-repository-markdown", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lint-repository-markdown- GitHub stars
- 214
- Token cost
- ~832 tokens
- SKILL.md length
- 359 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Keep the repository's linted Markdown passing npm run lint:markdown.
- Editing AGENTS.md
- SKILL.md covers Check before you push, What is linted, Configuration and The warnings that actually bite, plus 1 more section
- Calls npm; reaches codsen.com
- Any file under .agents/
What it does
Lint Repository Markdown is an agent skill from codsen/codsen. Keep the repository's linted Markdown passing npm run lint:markdown. Use when editing AGENTS.md, any file under .agents/ or .github/, or a package AGENTS.md, and whenever remark-lint reports a warning such as no-literal-urls, no-undefined-references, or list-item-indent.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting, Markdown and Agent instruction files. It works with npm and GitHub. The repository describes itself as: a monorepo of npm packages. The licence is MIT.
When your agent uses it
- Editing AGENTS.md
- Any file under .agents/
- A package AGENTS.md
- Whenever remark-lint reports a warning such as no-literal-urls
Example prompts
- “/lint-repository-markdown”
What it can do on your machine
Read from SKILL.md and the folder at commit e7e6df7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
codsen.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Lint Repository Markdown loads about 832 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 359 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from codsen/codsen at commit e7e6df7, republished under its MIT licence (© codsen). 359 words, ~832 tokens.
Download SKILL.mdSave it as
.claude/skills/lint-repository-markdown/SKILL.md (or your agent's skills folder).- name
- lint-repository-markdown
- description
- Keep the repository's linted Markdown passing `npm run lint:markdown`. Use when editing AGENTS.md, any file under .agents/ or .github/, or a package AGENTS.md, and whenever remark-lint reports a warning such as no-literal-urls, no-undefined-references, or list-item-indent.
Lint Repository Markdown
npm run lint:markdown runs remark over a fixed set of documentation files.
It passes --frail, so every warning is a CI failure. The Verify the repository step runs it early, and each later verification step is skipped
once it fails, which hides unrelated problems until the warning is fixed.
Check before you push
npm run lint:markdownnpm run check (Biome) does not cover Markdown. Biome reports
These paths were provided but ignored for a .md argument, which reads like
success but means the file was never inspected. Markdown is only ever validated
by the command above.
What is linted
Four globs, from the lint:markdown script in the root package.json:
AGENTS.md.agents/**/*.md, which includes everySKILL.md, this one included.github/**/*.mdpackages/*/AGENTS.md
Package README.md files are not linted here. lect generates them, so
fix their content at the generator or the source fields instead.
Configuration
.remarkrc.json loads remark-frontmatter, remark-gfm, and
remark-preset-lint-recommended. GFM is enabled, so tables, strikethrough, and
autolink literals all parse, and YAML frontmatter is understood. The preset
supplies these rules:
final-newline, list-item-bullet-indent, list-item-indent (one),
no-blockquote-without-marker, no-literal-urls, ordered-list-marker-style
(.), hard-break-spaces, no-duplicate-definitions,
no-heading-content-indent, no-shortcut-reference-image,
no-shortcut-reference-link, no-undefined-references, and
no-unused-definitions.
Show full SKILL.md (174 more words)Show less
The warnings that actually bite
no-literal-urls — a bare URL in prose. GFM turns it into an autolink
literal and the rule rejects it. This repository's house style wraps URLs in
backticks, which also stops a documentation URL becoming a live link:
See `https://codsen.com/os/examples` for the rendered list.Angle brackets satisfy the rule too, but only use them when the link is meant to be clickable.
no-undefined-references — square brackets that look like a reference
link but define nothing. Prose such as the [old] behaviour or a footnote
marker such as [1] triggers it. Escape the brackets as \[old\], or use
backticks.
no-shortcut-reference-link and no-shortcut-reference-image — the
[label] form, even when the definition exists. Write the full inline link.
list-item-indent — exactly one space after the bullet or number.
ordered-list-marker-style — 1. and never 1).
final-newline — end the file with a newline.
Reading the output
remark prints line:column-line:column, the severity, the message, and the
rule name:
AGENTS.md
488:10-488:40 warning Unexpected GFM autolink literal … no-literal-urlsFix the reported span, then re-run the command until every file reports
no issues found. Never silence a rule in .remarkrc.json to get a document
through; change the prose.
© codsen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/lint-repository-markdown of codsen/codsen.
Open the folder on GitHubat commit e7e6df7
Compare with similar skills
Lint Repository Markdown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Lint Repository Markdown this skillcodsen/codsen | 214 | — | ~832 | Automated safety check: Pass | MIT | |
| Update .NET Supported OS Matrixdotnet/core | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| README Badges and Headersjal-co/shieldcn | 916 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Releasehyhmrright/brooks-lint | 1.5k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Writing Docsc15t/c15t | 1.9k | — | ~872 | Automated safety check: Pass | Apache-2.0 | |
| Gemini Commit AgentJulian-adv/OpenMMO | 1.8k | — | ~383 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
README Badges and Headers
jal-co/shieldcn
Adds shadcn/ui-styled README badges, badge groups, download charts, header banners and sponsor or contributor grids using the shieldcn service.
Release
hyhmrright/brooks-lint
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG…
Writing Docs
c15t/c15t
Author or edit c15t documentation in docs//.mdx — the source for both the c15t.com site and the docs bundled into published packages.
Gemini Commit Agent
Julian-adv/OpenMMO
Automated quality-assured commit workflow. An agent skill from Julian-adv/OpenMMO.
Mdzilla
pi0/mdzilla
Browse, search, and export documentation from any source using the mdzilla CLI.
More from codsen/codsen
Calculate The Perf Performance
codsen/codsen
Run, audit, and interpret the Codsen monorepo performance benchmarks.
Maintain Node Compatibility
codsen/codsen
Audit, lower, test, and preserve Codsen package Node.js engine floors.
Related
Questions about Lint Repository Markdown
What does Lint Repository Markdown do?
Keep the repository's linted Markdown passing npm run lint:markdown. Lint Repository Markdown is an agent skill from codsen/codsen. Keep the repository's linted Markdown passing npm run lint:markdown.
When should I use Lint Repository Markdown?
Lint Repository Markdown fits situations like: editing AGENTS.md; any file under .agents/; A package AGENTS.md; whenever remark-lint reports a warning such as no-literal-urls.
How do I install Lint Repository Markdown in Claude Code?
Run `npx skills add codsen/codsen --skill lint-repository-markdown -a claude-code`. Or copy the skill folder (.agents/skills/lint-repository-markdown in codsen/codsen) into .claude/skills/lint-repository-markdown in your project. Claude Code loads it when a task matches its description.
How do I install Lint Repository Markdown in Codex?
Run `npx skills add codsen/codsen --skill lint-repository-markdown -a codex`. Or copy the skill folder (.agents/skills/lint-repository-markdown in codsen/codsen) into .agents/skills/lint-repository-markdown in your project. Codex loads it when a task matches its description.
Can I use Lint Repository Markdown in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codsen/codsen --skill lint-repository-markdown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lint-repository-markdown, .gemini/skills/lint-repository-markdown, .github/skills/lint-repository-markdown and .opencode/skills/lint-repository-markdown in your project.
What does Lint Repository Markdown need to run?
Going by SKILL.md and its folder, Lint Repository Markdown needs the command-line tools its instructions call (npm).
Does Lint Repository Markdown access the network?
SKILL.md names 1 domain. In commands or code: codsen.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Lint Repository Markdown safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Lint Repository Markdown use?
Lint Repository Markdown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Lint Repository Markdown use?
About 832 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Lint Repository Markdown?
Skills that share tags, products or a category with Lint Repository Markdown: Update .NET Supported OS Matrix (dotnet/core, 22k stars), README Badges and Headers (jal-co/shieldcn, 916 stars), Release (hyhmrright/brooks-lint, 1.5k stars) and Writing Docs (c15t/c15t, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Lint Repository Markdown?
codsen (a GitHub organization) maintains it in codsen/codsen, which has 214 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 29, 2026.
Source: codsen/codsen on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.