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-bdd-autopilot)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-bdd-autopilot"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-bdd-autopilot/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-bdd-autopilot"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-bdd-autopilot.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.00053 | $0.02214 |
| Opus 5 | $0.00026 | $0.01107 |
| Sonnet 5 | $0.00011 | $0.00443 |
| Haiku 4.5 | $0.00005 | $0.00221 |
Grade A, and why
doc-bdd-autopilot 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-bdd-autopilot
Purpose
Automated BDD generation pipeline. From upstream EARS (docs/03_EARS/), a
user prompt, or an implementation plan (IPLAN-*), it analyzes the source,
generates a complete BDD suite of Given-When-Then scenarios, validates
readiness, maintains BDD-00_index.md, and drives the audit↔fix cycle to a
passing ADR-Ready score — for one BDD or a batch.
Layer: 4. Upstream: EARS (with BRD/PRD trace) / prompt / IPLAN input. Downstream: a validated BDD + index entry.
Skill Dependencies
| Skill | Role |
|---|---|
../doc-bdd/SKILL.md |
BDD structure, YAML scenario schema, and authoring rules (generation) |
../doc-bdd-audit/SKILL.md |
quality gate (ADR-Ready scoring + findings) |
../doc-bdd-fixer/SKILL.md |
applies fixes from the audit report |
../doc-naming/SKILL.md |
element-ID standards |
Input Contract
Accepts: a target BDD id/path; an upstream EARS id/path; a free-text prompt; or an IPLAN path. Optional: score threshold (default 90), max fix iterations (default 3), batch list. With no explicit input, treat the request as a prompt.
Smart Document Detection
For each target, check whether the BDD already exists (nested folder
docs/04_BDD/BDD-NN_{slug}/):
- Missing → generate mode (from EARS / prompt / IPLAN).
- Exists → review & fix mode (audit, then fix if below threshold).
Determine deliverable_type (code/document/ux/risk/process) from the
inherited PRD/BRD chain. Verify the upstream EARS exists before generating.
Model precheck
Advisory, best-effort. Surfaces the model you recommended for this layer; it cannot switch the session model. Before invoking the driver:
- If
.claude/aidoc-flow.config.yamlis absent, or has nomodel.*keys, skip this section entirely (no output). - Resolve the recommended model:
model.per_layer.BDDif set, elsemodel.default. - Act on
model.precheck(warn|silent|block):warn(default) — print one line, then continue to the driver:ℹ BDD recommends model '<rec>'. If you're not on it, run /model <rec> (or set model.precheck: silent to hide this).silent— print nothing; continue.block— print the line above plusprecheck=block: confirm you want to draft on the current model, or run /model <rec> first., then wait for the user to confirm before continuing.
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 bd27345da068
- 5d ago Changed 3d47bbe311a7
- 8d ago First seen · 185 lines · 53 tokens per session scan A 2f4bef2dd6a2
doc-bdd-autopilot is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 2,214 once invoked, about $0.0003 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
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.