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-tdd-fixer)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-tdd-fixer"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-tdd-fixer/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-tdd-fixer"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-tdd-fixer.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.00047 | $0.04203 |
| Opus 5 | $0.00023 | $0.02101 |
| Sonnet 5 | $0.00009 | $0.00841 |
| Haiku 4.5 | $0.00005 | $0.00420 |
Grade A, and why
doc-tdd-fixer 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 4d 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
88% identical to doc-bdd-fixer — 159 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-tdd-fixer
Purpose
Read the latest audit report and apply fixes to a TDD, bridging
../doc-tdd-audit/SKILL.md and a passing TDD so the audit↔fix cycle can
converge.
Layer: 7 (TDD quality improvement).
Upstream: the TDD document + .aidoc/audit/07_TDD-audit.md.
Downstream: the fixed TDD + TDD-NN.F_fix_report_vNNN.md.
When to Use
After doc-tdd-audit returns FAIL, as part of an Audit → Fix → Audit loop.
Do not use without an audit report (run the audit first) or to create a new
TDD (use ../doc-tdd/SKILL.md / ../doc-tdd-autopilot/SKILL.md).
Input Contract
Consume the .aidoc/audit/07_TDD-audit.md report. Back up the TDD before
editing (tmp/backup/TDD-NN_<ts>/); on error, restore. Element-ID standards
come from ${CLAUDE_PLUGIN_ROOT}/framework/governance/ID_NAMING_STANDARDS.md; structure rules from
${CLAUDE_PLUGIN_ROOT}/framework/layers/07_TDD/TDD-TEMPLATE.yaml and README.md.
Remediate Mode
Resolve review_mode from .aidoc/profile.yaml; if unset, fall through
to the framework default team per the precedence chain in
${CLAUDE_PLUGIN_ROOT}/framework/governance/ADAPTATION.md. Same
fallback applies to other adaptation knobs (section_toggles).
team mode (per REVIEW_TEAM.md §Operations §Remediate)
- Read the audit report at
.aidoc/audit/07_TDD-audit.mdAND, when present, the per-persona slots under.aidoc/review/07_TDD/<TDD-id>/(where<TDD-id>is the short artifact ID, e.g.TDD-01).- Prefer the per-persona slots for the structured findings — stable ids, priorities, locations, recommendations.
- Slots are optional — when absent (e.g. single_pass run produced no synthesizer output), fall back to parsing the audit report's Findings sections directly.
- Resolve responsible lenses per finding. Each blocking finding
(P0 + P1) carries a
personasarray in the synthesizer's reduced form OR can be inferred from per-lens slot membership. Dispatch rules:- Single-lens finding (1 persona): dispatch that lens.
- Multi-lens finding (2+ personas): dispatch all listed
lenses in parallel. Each writes its own
<persona>.fix_<N>.jsonslot. The fix is accepted only when every dispatched lens returns no new P0/P1 (any one lens regressing reverts the patch). - No-persona / orphan finding (empty or missing
personas): dispatch the TDD crew's author lens (perREVIEW_CREWS.yaml:qa_leadfor TDD) as the default responsible reviewer.
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.
- 4d ago Changed 92b7f749c7b2
- 5d ago First seen · 327 lines · 47 tokens per session scan A dc7044902dd9
doc-tdd-fixer is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 4,203 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to doc-bdd-fixer, differing in 159 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.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
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.