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-initgit 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-init)<a href="https://agentmods.dev/skills/nozomi-koborinai/contextlint/contextlint-init"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/contextlint/contextlint-init/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-init"><img src="https://agentmods.dev/badge/skills/nozomi-koborinai/contextlint/contextlint-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 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 155 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 176 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 193 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 225 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 258 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.00146 | $0.03138 |
| Opus 5 | $0.00073 | $0.01569 |
| Sonnet 5 | $0.00029 | $0.00628 |
| Haiku 4.5 | $0.00015 | $0.00314 |
Grade A, and why
contextlint-init 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contextlint-init
Bootstrap contextlint into a repository. The goal: take the user from "no doc lint" to "contextlint running with a sensibly tuned config" without forcing them to read docs or hand-pick from 21 rules.
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 to "set up contextlint", "install contextlint", "init lint", "lint setup", "set up Markdown linting", "doc integrity check", or any equivalent phrasing
- After cloning or starting a doc-heavy repo (specs, ADRs, requirements, design docs)
- Even when the user doesn't name contextlint explicitly — they want the outcome, not the brand name
Triggering phrasings appear across many languages. A few illustrative samples (not exhaustive):
- English: "set up contextlint", "init markdown lint", "lint my docs"
- Japanese: "contextlint 入れて", "lint 環境整えて", "ドキュメントの整合性チェック導入したい"
- Chinese: "设置 contextlint", "添加 markdown 检查"
- Korean: "contextlint 설정해줘", "마크다운 린트 추가해"
Why this skill exists
contextlint has 21 rules across 7 categories. Asking the user to read each one and pick is a non-starter — they will close the page. This skill closes that gap by inspecting the actual repo and proposing a config tailored to the doc style. The user only confirms or refines.
Steps
1. Detect existing contextlint
Look for contextlint.config.json at the repo root or any parent directory.
- If found, stop and ask the user (in their language):
(overwrite)Re-init from scratch(add)Keep existing config, propose new rules to add based on a fresh doc scan(skip)Do nothing
- If not found, continue.
Why ask? Silently re-initializing destroys a tuned config; silently adding rules can trip CI for collaborators. The user owns their config — present options, don't decide for them.
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 · 267 lines · 146 tokens per session scan A 285bfa4b009f
contextlint-init is a skill published in the GitHub repository nozomi-koborinai/contextlint (42 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 146 tokens to every session and 3,138 once invoked, about $0.0007 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.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.