Borrowing it
Nothing to install: this file belongs to teabranch/open-responses-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/teabranch/open-responses-server/main/.claude/skills/markdownlint/SKILL.mdgit clone --depth 1 https://github.com/teabranch/open-responses-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/teabranch/open-responses-server/markdownlint)<a href="https://agentmods.dev/skills/teabranch/open-responses-server/markdownlint"><img src="https://agentmods.dev/badge/skills/teabranch/open-responses-server/markdownlint/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/teabranch/open-responses-server/markdownlint"><img src="https://agentmods.dev/badge/skills/teabranch/open-responses-server/markdownlint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.00566 |
| Opus 5.5 | $0.00021 | $0.00226 |
| Sonnet 5.5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
markdownlint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Markdownlint Skill
Lint all documentation markdown files and optionally auto-fix issues.
Quick Usage
Check all docs
bash .claude/skills/markdownlint/scripts/lint-docs.sh
Auto-fix fixable issues
bash .claude/skills/markdownlint/scripts/lint-docs.sh --fix
Check specific files
bash .claude/skills/markdownlint/scripts/lint-docs.sh docs/events-and-tool-handling.md
What Gets Linted
By default the script lints:
docs/*.md— top-level documentationindex.md— Jekyll home pageCLAUDE.md— repo guidance.claude/skills/**/*.md— skill definitions
Excluded by default:
docs/plan/— historical planning archivesdocs/prompts/— prompt templatesdocs/pip-publish-instructions.md— legacy docdocs/using-uv.md— legacy doc
Configuration
The script uses whichever config is found first:
- Project-level
.markdownlint-cli2.yaml(in repo root) - Global
~/.markdownlint-cli2.yaml - markdownlint built-in defaults
The global config disables:
- MD013 (line length) — too noisy for content-heavy docs and tables
- MD060 (table pipe spacing) — stylistic preference
Workflow
After editing any .md file:
- Run
bash .claude/skills/markdownlint/scripts/lint-docs.sh - If issues found, run with
--fixto auto-fix what can be fixed - Manually fix remaining issues
- Re-run to verify clean
Common Rules
| Rule | What It Checks |
|---|---|
| MD001 | Heading levels increment by one |
| MD004 | Consistent unordered list style (dashes) |
| MD009 | No trailing spaces |
| MD022 | Blank lines around headings |
| MD025 | Single H1 per document (use front matter title) |
| MD031 | Blank lines around fenced code blocks |
| MD032 | Blank lines around lists |
| MD040 | Fenced code blocks should have a language |
| MD047 | Files end with a single newline |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 85 lines · 53 tokens per session scan A bf5f9c5cfd62
markdownlint is a skill published in the GitHub repository teabranch/open-responses-server (184 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 566 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…
naga-config
A configuration-management skill for Naga, including its settings, connected tools, and imported skills.
naga_control
A control interface for changing Naga’s own running state and settings through a specific agent type.
live2d_controller
// 读取：system.characterbundle.loadcharacterskillsections -> system.config.buildtier1variables.characterbuiltinskillsprompt.
code-review
A code-review and quality-analysis skill written in Chinese. It is intended to inspect code, find potential problems, and suggest improvements.
document-writer
A professional writing skill for creating technical documents such as READMEs, API documentation, and user manuals.