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 agentmods add skills/ashkaan/contextium/spec-auditnpx skills add Ashkaan/contextium --skill spec-auditgit clone --depth 1 https://github.com/Ashkaan/contextiumWhat 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 | $0.00077 | $0.03099 |
| Opus 5 | $0.00039 | $0.01550 |
| Sonnet 5 | $0.00015 | $0.00620 |
| Haiku 4.5 | $0.00008 | $0.00310 |
Grade A, and why
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 3d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-audit — review the design before it becomes code
A SPEC is the cheapest place in the loop to be wrong. A missing boundary case costs one line to add here and a rewrite to add after the code exists. This skill attacks the SPEC while fixing it is still cheap.
Two reviewers run, and they have different jobs:
- The independent reviewer (
spec-review.sh) attacks the design — gaps, boundary cases, peers left inconsistent, a shape bigger than the ask. - The spirit-check agent reads only the user's verbatim ask and the behavior contract, and answers one question: does the SPEC describe the thing that was actually asked for? It catches the failure the design reviewer structurally cannot — a SPEC that is internally excellent and solves the wrong problem.
Critical
- The reviewer should not be the author. Claude wrote the SPEC, so a Claude
reviewer shares the blind spot that produced it.
spec-review.shruns the review on a different model when one is installed. When none is (exit 3), fall back to a fresh-context agent — and say so, in the summary and in the trailer, so nobody reads reduced independence as full independence. - A reviewer that could not run is a FAILED audit, not a clean one. Exit 1 and 124 mean the review did not happen. Report it unavailable; do not emit a passing trailer.
- Findings get fixed or argued, never deferred. Accept and Edit, or push back
with a reason and let round 2 settle it. "Track it for later" is not a third
option per
@rule:no-deferral. - Non-material edits skip. A typo fix does not spend a reviewer call. Step 1 decides that deterministically so the judgment is not re-litigated each time.
step-1-materiality — is this change worth a review?
bash .claude/skills/spec-audit/scripts/check-materiality.sh <spec-path>
material:<reason> runs the audit. non-material:<reason> emits the skipped
trailer and exits:
bash .claude/skills/spec-audit/scripts/format-trailer.sh skipped-non-material wording-polish
What ships with it
3 files 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.
- 3d ago First seen · 236 lines · 77 tokens per session scan A 2b0040aa6fbc
spec-audit is a skill published in the GitHub repository Ashkaan/contextium (32 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 3,099 once invoked, about $0.0004 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
agentic-code-orchestrator
Unified codebase manipulation, AI deployment, data analysis, and academic delivery engine. Absorbs 6 coding protocols + data-analysis + academic-delivery + spec-driven-dev.
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
social-physics-filter
Unified boundary enforcement, interpersonal diagnostic, and relational audit engine. Absorbs 40 psychology + 2 social protocols and all relationship case studies.
therapeutic-ifs
Unified inner work engine: Schema deconstruction (diagnosis) + IFS therapy (treatment). Absorbs: schema-deconstruction.
dashboard-builder
Build self-contained interactive HTML dashboards with charts, filters, and tables. Generates a single browser-openable file — no server or dependencies required.
bionic-decision-engine
Unified mathematical arbitrator for all resource allocation decisions — money, time, energy, relationships. Absorbs 46 decision protocols + 24 strategy protocols into one dense engine.