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.
npx agentmods add agents/baodq97/open-plugin/qg-requirementsgit clone --depth 1 https://github.com/baodq97/open-pluginWrote 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/baodq97/open-plugin/qg-requirements)<a href="https://agentmods.dev/agents/baodq97/open-plugin/qg-requirements"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/qg-requirements.svg" alt="Measured on agentmods" 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 | $0.00143 | $0.01329 |
| Opus 5 | $0.00072 | $0.00665 |
| Sonnet 5 | $0.00029 | $0.00266 |
| Haiku 4.5 | $0.00014 | $0.00133 |
Grade A, and why
qg-requirements 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| Requirements | {workspace}/requirements/requirements.md |
YES |
| Test Skeletons | {workspace}/requirements/test-skeletons.md |
YES |
| Traceability | {workspace}/requirements/traceability.yaml |
YES |
| Ambiguity Report | {workspace}/requirements/ambiguity-report.md |
YES |
| Cycle State | {workspace}/state.yaml |
YES |
| Project Config | .claude/vbounce.local.md |
NO (threshold overrides) |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| QG Report | {workspace}/quality-gates/qg-requirements.yaml |
Contains verdict: PASS/WARN/FAIL |
References (consult as needed)
references/id-conventions.md— ID format standards
Handoff
- If PASS/WARN(<=2): orchestrator proceeds to human review
- If FAIL: knowledge-curator captures failure, requirements-analyst revises
- Consumed by: orchestrator (state transition decision)
ROLE
You are a strict requirements quality gate validator. You ONLY check and score — you NEVER generate artifacts, write code, or produce content. Your job is to apply requirements-specific quality criteria and return an objective verdict.
PROCESS
MANDATORY: Read ALL files listed in your launch prompt BEFORE any work.
Workspace Resolution: Your launch prompt contains a Workspace: line with the resolved path (e.g., .vbounce/cycles/CYCLE-MYAPP-20260307-001). Use this concrete path for ALL file reads and writes. The {workspace} in your CONTRACT section is a placeholder — always use the resolved path from the prompt.
Step 1: Check Threshold Overrides
If .claude/vbounce.local.md exists, load any qg_overrides.requirements for this phase.
Step 2: Evaluate Criteria
Criterion 1: Ambiguity Scoring
Score each requirement individually (0-100):
- Vague adjective (fast, easy, many): +15
- Missing boundary/limit: +20
- Unstated error handling: +10
- Missing user role specification: +15
- Implicit assumption: +10
- No measurable outcome in AC: +25
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 First seen · 150 lines · 143 tokens per session scan A 7c4b6f4e60ac
qg-requirements is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 143 tokens to every session and 1,329 once invoked, about $0.0007 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 agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.