Borrowing it
Nothing to install: this file belongs to dogganidhal/noddde. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dogganidhal/noddde/main/.claude/skills/audit-spec/SKILL.mdgit clone --depth 1 https://github.com/dogganidhal/nodddeWrote 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/dogganidhal/noddde/audit-spec)<a href="https://agentmods.dev/skills/dogganidhal/noddde/audit-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/audit-spec/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/dogganidhal/noddde/audit-spec"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/audit-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Agent Snooping · line 52 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium MCP Rug Pull · line 77 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 79 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Agent Snooping · line 129 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00050 | $0.02193 |
| Opus 5.5 | $0.00020 | $0.00877 |
| Sonnet 5.5 | $0.00010 | $0.00439 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
audit-spec 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 2mo 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditor Agent: Steps 5-6 (Validate + Coherence Review + Docs)
You are the Auditor — the independent reviewer in the spec pipeline. You run in a separate context from the Builder that wrote the code. You have no memory of implementation decisions. This is by design — you bring fresh eyes.
Your job: Verify the implementation matches the spec's intent (not just its tests), then update documentation. Produce an Audit Report.
Your authority: You can PASS, FAIL (send back to Builder), or raise a CONCERN (escalate to developer). You must be specific and actionable — never vague.
Input
You receive from the Orchestrator:
- Spec path: e.g.,
specs/core/ddd/aggregate.spec.md - Build Report path:
specs/reports/<spec-name>.build-report.md - Cycle number: 1 (first review) or 2 (second review after Builder re-run)
Pipeline
Phase A: Validation (read-only)
├── Mechanical checks (from validate-spec)
└── Coherence review (NEW — intent alignment)
↓
Phase B: Documentation (write)
└── Update docs (from update-docs)
↓
Write Audit Report
Phase A: Validation
A1: Read Everything
- Read the spec completely — all sections, especially Behavioral Requirements, Invariants, Edge Cases.
- Read the source file (
source_filefrom spec frontmatter). - Read the test file (derive path from spec path per mapping rules).
- Read the Build Report for context on what the Builder did.
- Read dependency source files if the spec has
depends_on.
A2: Mechanical Checks
Follow the validate-spec procedure as documented in .claude/skills/validate-spec/SKILL.md:
-
Export coverage: Compare spec
exportsvs source file actual exports.- Missing exports = FAIL
- Extra unexported items = note (not a failure)
-
Behavioral requirement audit: For each numbered requirement:
- Is it implemented in the source? (grep/read)
- Is it tested? (check test file)
- Grade: implemented+tested / implemented-not-tested / not-implemented
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.
- 2mo ago First seen · 265 lines · 50 tokens per session scan A dc82328a5b8c
audit-spec is a skill published in the GitHub repository dogganidhal/noddde (52 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 2,193 once invoked, about $0.0002 per session on Opus 5.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
code-review-architecture
Architecture-focused code review covering hexagonal boundary violations, DDD anti-patterns, CQRS misuse, and microservices coupling issues. Applied in addition to the language-specific review skill when architecture markers are detected. Invoked when reviewing hexagonal architectures, DDD patterns, or microservices…
cratis-chronicle-client-typescript
Use when connecting a standalone Node.js process to Chronicle or diagnosing its decorators, discovery or client lifecycle. Not for React generated proxies or another language's client.
cratis-arc-command-typescript
Use when bootstrapping an Arc Node.js server or defining its TypeScript commands. Not for frontend proxy consumption, validation-only changes or server queries; use the corresponding Arc sibling.
cratis-arc-query-typescript
Use when declaring Arc Node.js read-model queries or observable endpoints. Not for React proxy consumption, server commands or Chronicle event materialization.
cratis-arc-validation-typescript
Use when adding rejection rules, state checks or validation assertions to an Arc Node.js server. Not for defining commands or queries, C# and JVM validators, or append-time uniqueness.
cratis-engineering-review-rounds
Use when choosing a review round, handling review feedback or requesting a delta since the last reviewed SHA. Not for review criteria (cratis-code-review), release-candidate grouping (cratis-engineering-release-trains) or waiting on CI checks (cratis-engineering-ci-gates).