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 rvdbreemen/adr-kit --skill lintgit clone --depth 1 https://github.com/rvdbreemen/adr-kitWrote 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/rvdbreemen/adr-kit/lint)<a href="https://agentmods.dev/skills/rvdbreemen/adr-kit/lint"><img src="https://agentmods.dev/badge/skills/rvdbreemen/adr-kit/lint.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.00021 | $0.00182 |
| Opus 5 | $0.00010 | $0.00091 |
| Sonnet 5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
lint 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 7d 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
Lint ADRs
Invoke explicitly with $adr-kit:lint when needed.
Resolve <plugin-root> from this installed skill. Use only bundled,
local ADR Kit tools and follow this canonical workflow:
- Run
python <plugin-root>/bin/adr-lint --strict <path-or-docs/adr>. - Report PASS, ADVISORY, FAIL, Open Questions, and migration notices separately with file and line citations; do not edit ADRs.
- For a Proposed ADR, translate actionable findings into the next client-native grill invocation.
Do not contact another model or mutate user-owned instructions.
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.
- 7d ago First seen · 19 lines · 21 tokens per session scan A 9af2a2b82d4a
lint is a skill published in the GitHub repository rvdbreemen/adr-kit (6 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 182 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
audit
Audit a documentation-led repo against its own conventions — contiguous ADR numbering, INDEX sync, plan/ coverage, required sections, status validity, cross-reference resolution, language mandate, ADR-privacy leaks into user-visible code, cross-worktree collisions (duplicate numbers, duplicate plan ownership, same ADR…
adr-compliance
This skill should be used when the user asks about "ADR compliance", "architecture compliance", "ADR audit", "enforce ADRs", "check code against ADRs", "ADR violations", or needs guidance on auditing code compliance with accepted architectural decision records.
okf-knowledge-format
Author and validate knowledge as OKF (Open Knowledge Format) bundles — a directory of markdown files with YAML frontmatter, where every concept is one .md file with a REQUIRED type field, reserved index.md/log.md files, bundle-relative cross-links, and a permissive conformance model. Use when standing up or…
review-export
Export CocoReview reports as markdown, html, or pdf-ready status artifacts. Usage: $review export markdown|html|pdf [report-path].
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
michel-packmind-engineer-review
Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping, hexagonal-architecture conformance, analytics-event wiring, UX copy, UI reactivity, CLI behavior, multi-tenancy safety, and…