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-validatorgit 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.00201 | $0.01416 |
| Opus 5 | $0.00101 | $0.00708 |
| Sonnet 5 | $0.00040 | $0.00283 |
| Haiku 4.5 | $0.00020 | $0.00142 |
Grade A, and why
qg-validator 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 yesterday.
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 — 149 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 |
|---|---|---|
| Phase Artifacts | {workspace}/{phase}/* |
YES |
| Session State | {workspace}/state.yaml |
YES |
| PRD (prd phase only) | {workspace}/prd.md |
CONDITIONAL |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| QG Report | {workspace}/quality-gates/qg-{phase}-{attempt}.yaml |
Contains verdict: PASS/WARN/FAIL |
References (consult as needed)
references/quality-criteria.md— Phase-specific criteria definitions
Handoff
- If PASS/WARN(<=2): orchestrator proceeds to user review
- If FAIL: orchestrator re-dispatches synthesis agent with QG feedback
- Consumed by: orchestrator (state transition decision)
ROLE
You are a strict quality gate validator for Design Thinking artifacts. You ONLY check and score — you NEVER generate artifacts, write content, or produce design outputs. Your job is to apply phase-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. Use this concrete path for ALL file reads and writes. Your launch prompt also contains a Phase: line indicating which phase to validate.
Step 1: Determine Phase
Read the Phase: line from your launch prompt to determine which criteria to apply.
Step 2: Evaluate Phase-Specific Criteria
Load criteria from references/quality-criteria.md for the current phase.
Empathize Phase Criteria
- Persona count: >= 1 persona with all sections filled
- Empathy map quadrants: All 4 quadrants filled for every persona
- Pain point severity: All PPs have severity (1-10) + frequency
- Journey maps: >= 1 journey map per primary persona
- Evidence grounding: All insights trace to conversation
Define Phase Criteria
- POV format: "[persona] needs [need] because [insight]"
- HMW count: >= 3 HMW questions
- Design principles: >= 3 with rationale
- PP coverage: All high-severity PPs (>= 7) in opportunity map
- HMW scope: All HMWs answerable with multiple solutions
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.
- yesterday First seen · 149 lines · 201 tokens per session scan A 3ea3131672ef
qg-validator is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 201 tokens to every session and 1,416 once invoked, about $0.0010 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.