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 priyanshuchawda/codeaudit --skill docs-claims-evidence-reviewgit clone --depth 1 https://github.com/priyanshuchawda/codeauditWrote 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/priyanshuchawda/codeaudit/docs-claims-evidence-review)<a href="https://agentmods.dev/skills/priyanshuchawda/codeaudit/docs-claims-evidence-review"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/codeaudit/docs-claims-evidence-review/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/priyanshuchawda/codeaudit/docs-claims-evidence-review"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/codeaudit/docs-claims-evidence-review.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.00036 | $0.00213 |
| Opus 5 | $0.00018 | $0.00106 |
| Sonnet 5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
docs-claims-evidence-review 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 10d 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
Docs Claims Evidence Review
Workflow
- Extract strong claims from README and docs.
- Classify claim strength: weak, moderate, or strong.
- Map each claim to file, test, or documentation evidence.
- Mark missing evidence explicitly.
- Recommend keep, weaken, remove, or add evidence.
Strong Claims
Never allow unsupported claims such as secure, production-ready, enterprise-grade, fully tested, scalable, robust, or battle-tested. Docs should stay positive but truthful.
Evidence Examples
- Security: middleware, auth checks, rate limits, headers, validation, threat model, security tests.
- Production-ready: deployment docs, env docs, smoke tests, error handling, observability.
- Fully tested: test framework, meaningful test files, coverage or test command evidence.
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.
- 10d ago First seen · 27 lines · 36 tokens per session scan A c2cebddfd61a
docs-claims-evidence-review is a skill published in the GitHub repository priyanshuchawda/codeaudit (1 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 213 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
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
pr-blocker-summarizer
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
ijfw-cross-audit
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit.
doc-drift
Use this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect four kinds of issues: outdated claims, mutually contradictory…