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 kurone-kito/idd-skill --skill idd-spec-auditgit clone --depth 1 https://github.com/kurone-kito/idd-skillWrote 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/kurone-kito/idd-skill/idd-spec-audit)<a href="https://agentmods.dev/skills/kurone-kito/idd-skill/idd-spec-audit"><img src="https://agentmods.dev/badge/skills/kurone-kito/idd-skill/idd-spec-audit/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/kurone-kito/idd-skill/idd-spec-audit"><img src="https://agentmods.dev/badge/skills/kurone-kito/idd-skill/idd-spec-audit.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.00100 | $0.02165 |
| Opus 5 | $0.00050 | $0.01082 |
| Sonnet 5 | $0.00020 | $0.00433 |
| Haiku 4.5 | $0.00010 | $0.00216 |
Grade A, and why
idd-spec-audit 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 9d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDD Spec Audit
Status
Dogfood-only. This skill lives at
.claude/skills/idd-spec-audit/ in the kurone-kito/idd-skill source
repository only. It has no canonical skills/ source and is not an
audit/sync-manifest.json syncPairs/fileSets entry, unlike
.claude/skills/issue-authoring/ (which mirrors skills/issue-authoring/)
— there is nothing to distribute to adopter repositories yet. See
Promotion checkpoint below.
scripts/audit-docs.mjs catches byte-level drift — sync-pair mismatches,
budgets, config-vs-instruction agreement — but not semantic drift: prose
that contradicts a sibling file, leaked session context, passages that
are not completable from a cold read, or wording that stalls an
autonomous step. This skill runs that check as N parallel LLM read
passes, adapted from mew-ton/soloscrum's define-pr-lifecycle audit
model.
Scope
- Audit targets (findings may cite these):
.github/instructions/**/*.md(includinglite/),skills/issue-authoring/**/*.md,CLAUDE.md, and.github/copilot-instructions.md. Audit these files even though.github/instructions/**is itself the generatedtargetside of anaudit/sync-manifest.jsonsync pair (mirrored fromidd-template/) — this skill audits the corpus a worker session actually reads, not theidd-template/source, so being a sync target never exempts a file here. - Reference-only inputs (read for R2/R4, never a finding target):
docs/idd-concept-ownership.md(R2's closed concept-index seed) anddocs/idd-autonomy-contract.md(R4's reversible/irreversible source of truth). Both are read in full every pass. - Out of scope as an audit target / finding source:
.claude/**(this skill never audits itself — no finding ever cites a file under.claude/**, though the skill necessarily reads its own bundle, thisSKILL.mdandreferences/report-template.md, to run at all) and every other file underdocs/**besides the two reference-only inputs above (summary docs rely on the files they cite by design, so they are not audited as if they were the primary spec; adocs/idd-*.mdmirror's own drift isaudit-docs.mjs's job, checked against itsidd-template/docs/source, not this skill's).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 182 lines · 100 tokens per session scan A e74b29a7628e
idd-spec-audit is a skill published in the GitHub repository kurone-kito/idd-skill (11 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 2,165 once invoked, about $0.0005 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
understand-diff
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks.
auto-test-code
A structured process for critically reviewing and testing software code. It records review findings, test plans, commands, results, and supporting files in a project workspace.
git-pr-review
A read-only reviewer for GitHub pull requests, which are proposed code changes submitted for review. It produces an evidence-based report about whether a pull request should be merged.
code-reviewer
Use when reviewing Spring Boot 4 / Java 17+ code with concrete files or diffs — pull requests, modules, or pasted Java/Spring sources — for migration risks, architecture boundary leaks, JSpecify null-safety gaps, security flaws, performance regressions, or Spring Data pitfalls. Not for Kotlin-only code, non-Spring…
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
code-reviewer
A code-review workflow that checks completed work against its requirements or plan before merging. It groups findings by severity and gives each issue a fix and a way to verify it.