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 skills/lyupro/skillforge-mcp/markdown-linternpx skills add lyupro/skillforge-mcp --skill markdown-lintergit clone --depth 1 https://github.com/lyupro/skillforge-mcpWrote 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/lyupro/skillforge-mcp/markdown-linter)<a href="https://agentmods.dev/skills/lyupro/skillforge-mcp/markdown-linter"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/markdown-linter.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 | $0.00023 | $0.00362 |
| Opus 5 | $0.00012 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
markdown-linter 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 4d 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
This is a script-strategy skill. The script in scripts/main.py reads the Markdown file path from SKILLFORGE_INPUT, runs a built-in linter against it (no third-party dependencies — only the Python standard library), and prints findings to stdout, one per line.
Output format (one finding per line):
<line_number>:<column>:<severity>:<rule>:<message>
Severities: error, warning, info. Rules:
heading-order— H2 follows H1, H3 follows H2, no skipped levels.trailing-whitespace— lines ending in space or tab.tab-indent— tabs used for indent (Markdown prefers spaces).missing-alt—with empty alt text.bare-url— http(s) URL not wrapped in<...>or[text](url).mixed-list-marker— list switches between-,*,+inside the same block.
When the file does not exist or SKILLFORGE_INPUT is empty, the script prints 0:0:error:io:no input file and exits 0.
Prerequisites:
config.security.allowScripts: true.python3on the host's resolvedPATH.SKILLFORGE_INPUTset to the absolute path of the.mdfile to lint.
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.
- 4d ago First seen · 36 lines · 23 tokens per session scan A b380a8d22de5
markdown-linter is a skill published in the GitHub repository lyupro/skillforge-mcp (1 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 362 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 skills, from other repositories
eli5
Transform technical jargon into clear explanations using before/after comparisons, metaphors, and practical context.
documentation-style
NVCF public docs style: short, plain, ASCII Markdown with no bold, emojis, em-dash, or en-dash. Use when editing public docs, READMEs, AGENTS.md, agent skills, plans, GitHub issues, or GitHub Pull Request descriptions.
pr
Creates and updates GitHub pull requests for cloudflare-docs changes. Load when asked to open, create, submit, update, or edit a PR, or write a PR title or description. Covers title conventions, branch naming, PR body structure, and the documentation checklist template.
slopless
Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, and cliches.
workers-code-review
Reviews Workers and Cloudflare Developer Platform code for type correctness, API usage, and configuration validity. Load when reviewing TypeScript/JavaScript using Workers APIs, wrangler.jsonc/toml config, or Cloudflare bindings (KV, R2, D1, Durable Objects, Queues, Vectorize, AI, Hyperdrive).
contributing
Use when contributing to the Cloudflare Docs repository — writing or editing documentation pages, choosing content types or components, adding changelog entries, reviewing docs, or learning how to contribute.