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-impactgit 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-impact)<a href="https://agentmods.dev/skills/nozomi-koborinai/contextlint/contextlint-impact"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/contextlint/contextlint-impact/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-impact"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/contextlint/contextlint-impact.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 75 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 150 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 161 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.00113 | $0.02483 |
| Opus 5 | $0.00056 | $0.01241 |
| Sonnet 5 | $0.00023 | $0.00497 |
| Haiku 4.5 | $0.00011 | $0.00248 |
Grade A, and why
contextlint-impact 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 12d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contextlint-impact
Analyze the impact of changing or deleting a Markdown document using contextlint's Context Graph engine. Tells the user not just which files reference the target directly, but the transitive cascade — and surfaces orphans, hubs, and cycles that grep can't see.
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 to match the user's language at runtime.
When to use this skill
- The user asks "what breaks if I change X?", "what depends on this doc?", "is it safe to delete this file?", "I want to refactor X, what's the impact?"
- The user is planning a doc restructure or rename
- The user is verifying after a change that all dependents were updated
- The user wants to understand cross-doc dependencies before mass-editing
- Even when contextlint isn't named explicitly — the user wants the answer, not the brand
Triggering phrasings appear across many languages. A few illustrative samples (not exhaustive):
- English: "what breaks if I change design.md?", "is FR-101 safe to delete?", "show me what depends on this doc"
- Japanese: "design.md 変更したら何壊れる?", "FR-101 削除して大丈夫?", "依存関係知りたい"
- Chinese: "修改 design.md 会影响什么?", "删除这个文件安全吗?"
- Korean: "design.md 바꾸면 뭐가 깨져?", "이 파일 삭제해도 돼?"
Why this skill exists
contextlint has a Context Graph engine that other linters don't have. In an AI era where docs get mass-edited (and AI agents themselves modify multiple files at once), tracking the cascade of cross-references becomes critical:
grepshows direct mentions but misses transitive impact- Human intuition can't trace transitive dependencies across a 100-file repo
- AI mass-edits without impact awareness leave broken refs scattered across the doc graph
This skill exposes the graph engine through one simple question: "what breaks if I touch this?"
Steps
1. Verify contextlint is set up
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.
- 12d ago First seen · 192 lines · 113 tokens per session scan A d4389e8d2056
contextlint-impact is a skill published in the GitHub repository nozomi-koborinai/contextlint (42 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 2,483 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…