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-brd-fixer)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/doc-brd-fixer"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-brd-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-brd-fixer"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/doc-brd-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.00044 | $0.04204 |
| Opus 5 | $0.00022 | $0.02102 |
| Sonnet 5 | $0.00009 | $0.00841 |
| Haiku 4.5 | $0.00004 | $0.00420 |
Grade A, and why
doc-brd-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 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doc-brd-fixer
Purpose
Read the latest audit report and apply fixes to a BRD, bridging
../doc-brd-audit/SKILL.md and a passing BRD so the audit↔fix cycle can
converge.
Layer: 1 (BRD quality improvement).
Upstream: the BRD document + .aidoc/audit/01_BRD-audit.md.
Downstream: the fixed BRD + BRD-NN.F_fix_report_vNNN.md.
When to Use
After doc-brd-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
BRD (use ../doc-brd/SKILL.md / ../doc-brd-autopilot/SKILL.md).
Input Contract
Consume the latest audit report from .aidoc/audit/01_BRD-audit.md (the
.aidoc/ provenance tier). Back up the BRD before editing
(tmp/backup/BRD-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/01_BRD/BRD-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/01_BRD-audit.mdAND, when present, the synthesizer'sverdict.json+ per-persona slots at.aidoc/review/01_BRD/<BRD-id>/(where<BRD-id>is the short artifact ID, e.g.BRD-01).- Prefer
verdict.jsonfor the blocking-findings count and coverage summary — it is the deterministic JSON written by the synthesizer (agents/synthesizer.md). - Prefer the per-persona slots for the structured findings — stable ids, priorities, locations, recommendations.
- Slots and verdict.json are optional — when absent (e.g. single_pass run produced no synthesizer output), fall back to parsing the audit report's Findings sections directly.
- Prefer
- Resolve responsible lenses per finding. Each blocking finding
(P0 + P1) carries a
personasarray in the synthesizer's reduced form (seeverdict.json:findings[*].personas) OR can be inferred from per-lens slot membership. Dispatch rules:- Single-lens finding (1 persona): dispatch that lens.
- Multi-lens finding (2+ personas, e.g. an
architect+business_analyst contradiction): 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 BRD crew's author lens (perREVIEW_CREWS.yaml:business_analystfor BRD) as the default responsible reviewer. Falling back to author-lens rather than skipping ensures every blocking finding gets at least one validation pass. P2/P3 are advisory — apply deterministically without lens validation.
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 ff56e9564b66
- 4d ago Changed 78677d438fc0
- 8d ago First seen · 328 lines · 44 tokens per session scan A 000497d22a04
doc-brd-fixer is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 4,204 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…