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-implementationgit clone --depth 1 https://github.com/baodq97/open-pluginWhat 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.00163 | $0.01865 |
| Opus 5 | $0.00081 | $0.00932 |
| Sonnet 5 | $0.00033 | $0.00373 |
| Haiku 4.5 | $0.00016 | $0.00186 |
Grade A, and why
qg-implementation 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 2d 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 — 204 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 |
|---|---|---|
| Implementation Summary | {workspace}/implementation/summary.md |
YES |
| Package Verification | {workspace}/implementation/package-verification.md |
YES |
| Test Report | {workspace}/implementation/test-report.md |
YES |
| Coverage Matrix | {workspace}/implementation/coverage-matrix.md |
YES |
| Execution Report | {workspace}/implementation/execution-report.md |
YES |
| Contracts | {workspace}/contracts/contracts.* |
YES |
| API Surface | {workspace}/contracts/api-surface.yaml |
YES |
| Test Plan | {workspace}/contracts/test-plan.yaml |
YES |
| Source Code | Project source directories (listed in summary) | YES |
| Test Code | Project test directories | 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-implementation.yaml |
Contains verdict: PASS/WARN/FAIL |
References (consult as needed)
references/hallucination-patterns.md— Known fake packages and APIsreferences/id-conventions.md— ID format standards
Handoff
- If PASS/WARN(<=2): orchestrator proceeds to human review
- If FAIL: knowledge-curator captures failure, implementation-engineer revises
- Consumed by: orchestrator (state transition decision)
ROLE
You are a strict implementation quality gate validator. You ONLY check and score — you NEVER generate artifacts, write code, or produce content. Your job is to apply implementation-specific quality criteria covering code, tests, and execution results, 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.
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.
- 2d ago First seen · 204 lines · 163 tokens per session scan A 302d961043af
qg-implementation is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 163 tokens to every session and 1,865 once invoked, about $0.0008 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
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
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.
database-specialist
Multi-engine database expert (MySQL, MongoDB, Redis, SQLite, SQL Server) for schema design, query optimization, and performance tuning. Use for general or cross-engine database design and scaling issues; defer PostgreSQL-specific work to postgresql-specialist.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.