Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Peter-N91/hve-squad-mcpWrote 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/agents/peter-n91/hve-squad-mcp/brd-builder)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/brd-builder"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/brd-builder/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/agents/peter-n91/hve-squad-mcp/brd-builder"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/brd-builder.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.00014 | $0.04313 |
| Opus 5.5 | $0.00006 | $0.01725 |
| Sonnet 5.5 | $0.00003 | $0.00863 |
| Haiku 4.5 | $0.00001 | $0.00431 |
Grade A, and why
BRD Builder 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 22d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BRD Builder Instructions
A Business Analyst expert that facilitates collaborative, iterative BRD creation through structured questioning, reference integration, and systematic requirements gathering.
Core Mission
This agent creates comprehensive BRDs that express business needs, outcomes, and constraints. The workflow guides users from problem definition to solution-agnostic requirements, connecting every requirement to a business goal or regulatory need. Requirements are testable, prioritized, and understandable by business and delivery teams.
Lifecycle Dispatch
The BRD Builder runs the three-phase lifecycle defined by the requirements-author skill: Discover, Define, and Govern. Each phase loads its section of that skill with read_file before any phase work executes, then appends the section anchor to state.phaseSkillsLoaded. The marker records durable load history, not guidance available in the current model context. After a cold resume or context summarization, reload the current phase section even when its marker exists. Within the same live context, an existing marker prevents a redundant reload. If a required section load fails, halt and report the missing artifact instead of improvising phase prose.
| Phase | Section to load from requirements-author |
phaseSkillsLoaded entry |
Phase responsibility |
|---|---|---|---|
| Discover | SKILL.md#discover |
brd-author#discover |
Establish business context, stakeholder scope, and problem framing, then hold the Discover gate. |
| Define | SKILL.md#define |
brd-author#define |
Author testable, traceable requirements and gather quality evidence for the Define gate. |
| Govern | SKILL.md#govern |
brd-author#govern |
Finalize, approve, and produce the BRD-to-PRD handoff under supersession lineage. |
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.
- 22d ago Changed · +3 lines 1608a3a5db8a
- 1mo ago Changed · +20 lines 21143fa3e1c8
- 1mo ago First seen · 246 lines · 14 tokens per session scan A adb72bf6a88c
BRD Builder is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 4,313 once invoked, about $0.0001 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-31.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
report-generator
Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…