Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vladm3105/aidoc-flow-framework/plugin install aidoc-flowWrote 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/vladm3105/aidoc-flow-framework/doc-spec-audit)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-spec-audit"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-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/vladm3105/aidoc-flow-framework/doc-spec-audit"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-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.00037 | $0.07025 |
| Opus 5 | $0.00018 | $0.03513 |
| Sonnet 5 | $0.00007 | $0.01405 |
| Haiku 4.5 | $0.00004 | $0.00702 |
Grade A, and why
doc-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.
This is a copy
83% identical to doc-bdd-audit — 163 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-spec-audit
Purpose
Run a unified SPEC audit — declarative structural checks plus content-quality
review — in one pass, producing a single combined report that
../doc-spec-fixer/SKILL.md consumes. The framework ships no runtime code, so
this skill is the validator: Claude performs each check directly against the
SPEC using the spec as the contract.
Layer: 6 (SPEC quality gate). Upstream: a SPEC file. Downstream:
.aidoc/audit/06_SPEC-audit.md and an optional fix-cycle trigger.
When to Use
Use after a SPEC exists and before generating the TDD, or inside the autopilot's
audit↔fix cycle. Do not use to create a SPEC (use ../doc-spec/SKILL.md or
../doc-spec-autopilot/SKILL.md).
Fresh-audit policy: always audit from scratch — never reuse prior scores or cached results; compute the TDD-Ready score independently each run.
Report cleanup: the audit report is a single file
(.aidoc/audit/06_SPEC-audit.md) overwritten in place each run — no version cleanup
needed. Keep SPEC-NN.F_fix_report_v*.md and .drift_cache.json.
Execution Contract
Input: SPEC path (docs/06_SPEC/SPEC-NN_*/...); optional score threshold
(default 90).
Sequence: 1) run structural checks → 2) record findings → 3) run content
review → 4) merge/normalize findings → 5) write .aidoc/audit/06_SPEC-audit.md
→ 6) if auto-fixable findings exist, hand off to doc-spec-fixer.
Review Mode
Resolve review_mode from .aidoc/profile.yaml; if the key is unset
(the project profile is an override-only delta — most knobs are absent),
fall through to the framework default per the precedence chain in
${CLAUDE_PLUGIN_ROOT}/framework/governance/ADAPTATION.md (framework defaults < user-global seed < project profile). The framework default
is team at gates (pre_promotion / pre_merge) and single_pass at
write-time (on_author). The same fallback rule applies to every other
adaptation knob (audit_threshold, section_toggles, active_layers,
glossary). The structural checks below are run deterministically by
this skill in every mode — they are the gate floor per
${CLAUDE_PLUGIN_ROOT}/framework/governance/REVIEW_TEAM.md §"Scoring,
conflicts & the gate".
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 Changed 563889be404e
- 4d ago First seen · 593 lines · 37 tokens per session scan A 474eb1eb84d8
doc-spec-audit is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 7,025 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to doc-bdd-audit, differing in 163 lines, and is treated as a copy.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.