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/design-architectgit 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.00315 | $0.02213 |
| Opus 5 | $0.00158 | $0.01107 |
| Sonnet 5 | $0.00063 | $0.00443 |
| Haiku 4.5 | $0.00032 | $0.00221 |
Grade A, and why
design-architect 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 — 191 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 |
| Tech Context | {workspace}/tech-context.yaml |
YES |
| Tech Context Prompt | {workspace}/tech-context-prompt.md |
NO |
| Cycle State | {workspace}/state.yaml |
YES |
| Learned Rules | .claude/rules/vbounce-learned-rules.md |
NO |
| Project Config | .claude/vbounce.local.md |
NO |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Architecture Design | {workspace}/design/design.md |
Contains component diagrams (Mermaid), sequence diagrams |
| Security Design | {workspace}/design/security-design.md |
Contains STRIDE analysis for every component |
| API Specification | {workspace}/design/api-spec.md |
Every US-* maps to >= 1 endpoint |
| Database Schema | {workspace}/design/database-schema.md |
Contains ER diagram (Mermaid), migration plan |
| ADRs | {workspace}/design/architecture-decisions.md |
>= 1 ADR with alternatives considered |
| Traceability | {workspace}/design/traceability.yaml |
REQ->Story->API->Component->STRIDE->ADR |
| Test Impact | {workspace}/design/test-impact.md |
Unit/Integration/Security test plan |
| Test Specifications | {workspace}/design/test-specifications.md |
ITS-, STS-, SECTS-* specs |
References (consult as needed)
references/architecture-patterns.md— Architecture styles and design patternsreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-design (phase=design)
- Consumed by: implementation-engineer, traceability-analyst
ROLE
You are an elite software architect and security design specialist with deep expertise in Clean Architecture, CQRS, distributed systems, API design, threat modeling (STRIDE), and technical documentation. You produce designs that are precise, traceable, secure, and implementable.
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 · 191 lines · 315 tokens per session scan A ac46f6aaa177
design-architect is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 315 tokens to every session and 2,213 once invoked, about $0.0016 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.
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.