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 kunalsuri/ai-fication-kit --skill review-agent-configgit clone --depth 1 https://github.com/kunalsuri/ai-fication-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/kunalsuri/ai-fication-kit/review-agent-config)<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/review-agent-config"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/review-agent-config/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/kunalsuri/ai-fication-kit/review-agent-config"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/review-agent-config.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.01306 |
| Opus 5 | $0.00023 | $0.00653 |
| Sonnet 5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
review-agent-config 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the review-agent-config diagnostic. Read-only. Produce a structured findings report; do NOT edit any file.
Inputs — read these files (and only these)
CLAUDE.md(project root) — full readAGENTS.md(project root) — full readpackage.json(project root) — grep for"build"and"test"script keys onlypom.xml(project root, if present) — grep<build>section onlyai/guide/MODULE_MAP.md— check existence on disk; no deep read neededai/INDEX.md— check existence on disk; no deep read needed- Any
ai/guide/*.mdpaths referenced in the knowledge-map sections — existence check only via Glob
Checks
Section A — CLAUDE.md structure
| ID | Check | Severity |
|---|---|---|
| C1 | Contains the literal @AGENTS.md directive (not just a comment or a markdown link [AGENTS.md](AGENTS.md)) |
❌ |
| C2 | Has a "Hard rules" or equivalent section | ❌ |
| C3 | Has a "Where to look" or knowledge-map section with explicit pointers into ai/guide/ |
❌ |
| C4 | Has a token-discipline or subagent-delegation section | ⚠️ |
| C5 | No unfilled placeholders: regex <[a-zA-Z ]{3,}>, bare TODO, or the literal string fill in |
❌ |
| C6 | Build command is present and not a placeholder | ❌ |
| C7 | Test command is present and not a placeholder | ❌ |
| C8 | Test locations are filled in (not <fill in during cold start> or equivalent) |
❌ |
| C9 | No reference to CLAUDE_bkp_*.md files framed as active guidance (stale post-cold-start) |
⚠️ |
| C10 | No Claude-specific directives duplicated wholesale from AGENTS.md | ⚠️ |
Section B — AGENTS.md structure
| ID | Check | Severity |
|---|---|---|
| A1 | Contains no Claude Code-specific directives (@import, memory syntax, hook syntax) |
⚠️ |
| A2 | Hard rule present: frozen upstream / don't touch inherited code | ❌ |
| A3 | Hard rule present: test before done — with actual build and test commands | ❌ |
| A4 | Hard rule present: surgical diffs | ❌ |
| A5 | Hard rule present: provenance tagging ([inferred] / [verified]) |
❌ |
| A6 | Hard rule present: no phantom bugs / config churn | ❌ |
| A7 | Hard rule present: verify claims before declaring done | ❌ |
| A8 | Hard rule present: license-header matching for new files | ⚠️ |
| A9 | Has a knowledge-map section pointing to ai/guide/ |
❌ |
| A10 | No unfilled placeholders (same regex as C5) | ❌ |
| A11 | No reference to AGENTS_bkp_*.md files framed as active guidance |
⚠️ |
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 · 105 lines · 45 tokens per session scan A a474957be860
review-agent-config is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 9d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,306 once invoked, about $0.0002 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
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
codebase-audit
A read-only method for auditing an entire codebase across contracts, data integrity, errors, security, architecture, technical debt, configuration, and caching. It produces prioritized findings and a repair roadmap.
codex-agent
Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.