Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/s2005/markdown-linter-fixer-skill/mdlintergit clone --depth 1 https://github.com/s2005/markdown-linter-fixer-skillWrote 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/commands/s2005/markdown-linter-fixer-skill/mdlinter)<a href="https://agentmods.dev/commands/s2005/markdown-linter-fixer-skill/mdlinter"><img src="https://agentmods.dev/badge/commands/s2005/markdown-linter-fixer-skill/mdlinter.svg" alt="Measured on agentmods" 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.00010 | $0.00601 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
mdlinter 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 6d 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
Markdown Linter - {{ARGUMENTS}}
Use the markdown-linter-fixer skill to check or fix markdown linting issues.
Command format: /markdown-linter-fixer:mdlinter [mode] [scope]
Arguments:
-
Mode (optional):
{{ARGUMENTS}}- First argument can be either
checkorfix check- scan and report issues WITHOUT making changes (DEFAULT if not specified or invalid)fix- scan and automatically fix all issues- Safety default: If no mode is provided or an invalid mode is given, defaults to
checkmode
- First argument can be either
-
Scope (optional):
- Can be specified as second argument (or first if mode is omitted)
- Can be: a specific file, multiple files (space-separated), a folder, or a glob pattern
- If not provided, operates on ALL markdown files in the project
Examples:
/markdown-linter-fixer:mdlinter- check all files (default mode)/markdown-linter-fixer:mdlinter check- explicitly check all files/markdown-linter-fixer:mdlinter fix- fix all files/markdown-linter-fixer:mdlinter README.md- check only README.md (default mode)/markdown-linter-fixer:mdlinter check README.md- explicitly check only README.md/markdown-linter-fixer:mdlinter fix docs/- fix all files in docs folder/markdown-linter-fixer:mdlinter check README.md CONTRIBUTING.md- check specific files
Workflow based on mode:
IMPORTANT: If mode is not specified or is invalid, always use CHECK mode as the safe default.
For CHECK mode:
- Verify markdownlint-cli2 installation
- Check for existing configuration files
- Run diagnostic scans on the specified scope
- Categorize and analyze all errors by type
- Generate comprehensive report
- IMPORTANT: Do NOT execute auto-fix (--fix flag)
- Do NOT make any manual fixes to files
- ONLY scan and report the issues found
For FIX mode:
- Verify markdownlint-cli2 installation
- Check/create configuration files
- Run diagnostic scans on the specified scope
- Apply automatic fixes using --fix flag
- Handle any remaining manual fixes (especially MD029 issues)
- Verify all issues are resolved
- Provide comprehensive summary report
Report should include:
- Total files scanned
- All errors found by type (MD001, MD029, MD032, etc.)
- File names and line numbers for each error
- Count of each error type
- Which errors are auto-fixable vs require manual intervention
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.
- 6d ago First seen · 66 lines · 10 tokens per session scan A 450896a8ffd2
mdlinter is a command published in the GitHub repository s2005/markdown-linter-fixer-skill (10 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 601 once invoked, about $0.0001 per session on Opus 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-31.
Other commands, from other repositories
research-l2
Executes Phases 1-3 of the L2 process of the abapwiki knowledge base on a slice: launches the abap-functional-researcher sub-agent (gap discovery + multi-source auto-research: wiki -> raw/docs -> MCP abap-fs on the system read-only -> standard knowledge), ingests gaps and evidence, and generates questionnaires for…
capture-answer
Ingests an expert's answers to an L2 questionnaire in the abapwiki knowledge base: transforms the answers (filled in the interviews/ file or given verbally) into a canonical citable expert-answer (slices/ /inputs/expert-answers/), moves gaps to 'answered' and closes the questions. Use this skill when the owner/expert…
ingest-l0
L0 bootstrap of the abapwiki knowledge base: creates stubs for all custom objects from the TADIR. Use this skill to initialize the repo from scratch or to ingest a new TADIR export. Deterministic operations (no LLM sub-agent), idempotent.
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
lint-audit
Checks the integrity of the abapwiki knowledge base: parseable YAML frontmatter, no broken wikilinks, resolvable [VERIFIED: path:N-M] citations, non-nested confidence tags, drift between wiki and DB, synchronization between canonical agent contracts and the .claude/agents/ copies. Use this skill periodically or after…
query
Queries the abapwiki knowledge base to answer questions about custom ABAP code (what an object does, which tables it uses, who calls it, dependencies, bugs). Navigates index -> package -> pages; can extend the answer with the SAP system via MCP abap-fs in read-only mode, explicitly citing wiki vs. system.