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 skills add nozomi-koborinai/contextlint --skill contextlint-fixgit clone --depth 1 https://github.com/nozomi-koborinai/contextlintWrote 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/nozomi-koborinai/contextlint/contextlint-fix)<a href="https://agentmods.dev/skills/nozomi-koborinai/contextlint/contextlint-fix"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/contextlint/contextlint-fix/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/nozomi-koborinai/contextlint/contextlint-fix"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/contextlint/contextlint-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 72 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 101 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00118 | $0.01604 |
| Opus 5 | $0.00059 | $0.00802 |
| Sonnet 5 | $0.00024 | $0.00321 |
| Haiku 4.5 | $0.00012 | $0.00160 |
Grade A, and why
contextlint-fix 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contextlint-fix
Run contextlint over the project's structured Markdown and apply fixes for the violations it detects.
Language note: This skill is used across many languages. Respond to the user in their primary language (the one they're typing in). The English prompts and outputs below are reference templates — translate them at runtime.
When to use this skill
- The user asks to "fix lint errors", "clean up docs", "repair broken Markdown links", "run contextlint"
- After bulk changes to Markdown files (especially AI-generated specs / ADRs)
- Before committing changes that touch docs / specs / ADRs
- Even when the user doesn't name contextlint explicitly — they want the outcome (clean, valid docs)
Triggering phrasings appear across many languages. A few illustrative samples:
- English: "fix lint errors", "clean up the broken links in docs", "fix what contextlint is complaining about"
- Japanese: "contextlint がエラー出してるから直して", "lint 直して", "壊れたリンク直して"
- Chinese: "修复 markdown 错误", "清理文档"
- Korean: "lint 오류 고쳐줘", "문서 정리해줘"
Why this skill exists
Doc rot (broken cross-refs, missing sections, leftover TODOs) accumulates silently. Manual cleanup is tedious and easy to skip. AI agents bulk-editing docs also accumulate violations as a side effect. This skill turns "go fix the lint output" into a one-step request, while being careful to never silently mutate semantic content — only mechanical fixes are auto-applied.
Steps
1. Verify contextlint is set up
- Check for
contextlint.config.jsonin the repo root or any parent directory - Check that
@contextlint/cliis available (devDependenciesornpx) - If not set up, suggest the
contextlint-initskill first
Why? Without a config, contextlint can't run. Without cross-file rules enabled, many fix opportunities won't surface.
2. Run lint
npx contextlint
For machine-readable parsing in step 3, add --format json.
3. Parse output and apply fix strategies
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.
- 11d ago First seen · 123 lines · 118 tokens per session scan A 4da23d1668a0
contextlint-fix is a skill published in the GitHub repository nozomi-koborinai/contextlint (42 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 118 tokens to every session and 1,604 once invoked, about $0.0006 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-30.
Other skills, from other repositories
slopless
Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, and cliches.
suiko
A Japanese writing and review workflow for checking whether text sounds uniform, translated, unnatural, or difficult to read. It supports writing and editing documents such as reports, guides, meeting notes, proposals, and emails.
slop-chop
Remove AI writing tells from text with the slop-chop CLI. Use when the user wants to clean up a draft, strip em-dashes, semicolons, and stock buzzwords, enforce a spelling dialect, or make text read like a person wrote it instead of a chatbot. Also use before handing back a written draft, or to flag slop in Markdown…
stop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
processing-markdown
Processes Markdown files using mq, a jq-like query language for Markdown. Use when the user mentions Markdown processing, content extraction, document transformation, or mq queries.
web-scraping
Fetches web pages and extracts structured data using mq's toolchain (mq-crawl for fetching/crawling/JS rendering, mq for HTML-to-Markdown selector-based extraction, http() for in-query requests). Use when the user wants to scrape a URL, pull structured data out of a webpage, crawl a site, or turn HTML into…