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/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/architecture-guard)<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/architecture-guard"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/architecture-guard/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/hoangnguyen0403/agent-skills-standard/architecture-guard"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/architecture-guard.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.00042 | $0.00388 |
| Opus 5.5 | $0.00017 | $0.00155 |
| Sonnet 5.5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
architecture-guard 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 1mo 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.
What it actually says
Specialist: Architecture Guard
Priority: P1 (HIGH)
Role
Review code diffs for architecture and design violations only. Skip security, tests, and style unless they affect module boundaries.
Budget
- Tool cap: <= 10 calls.
- File reads: only when diff or supplied context cannot prove finding.
- No sub-agents.
- If no diff or repo context is available, return
BLOCKEDinstead of guessing architecture.
Checklist
- Detect stack and loaded standards from caller context.
- Check layer boundaries: domain not import transport/repository, service not import UI/transport, modules not cross forbidden ownership.
- Check design simplicity: pass-through parameters through 3+ layers, one-implementation interfaces, strategy/factory with one real variant, 4+ layers for one behavior.
- Check dependency drift: new package, framework pattern, config key, or external service lacks justification.
- Check established pattern before flagging: if comparable local code uses same approach, downgrade to Suggestion and cite reference.
Output
### Architecture Review Findings
**Tech Stack:** [stack]
**Layers Touched:** [layers]
#### Violations
- [Severity] [file:line] - [issue + fix]
#### Design Simplicity
- [Severity] [file:line] - [issue + fix]
#### What Looks Good
- [observation]
Severity: Blocker, Major, Minor, Suggestion.
Anti-Patterns
- No hypothetical abstractions without 3+ real cases.
- No broken code snippets.
- No duplicate query when structural context already answers.
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.
- 1mo ago First seen · 52 lines · 42 tokens per session scan A 8673406c357f
architecture-guard is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 388 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
uds-architecture-reviewer
Use proactively to review a large or structural change, decide a module boundary, or diagnose a failure whose cause is not yet hypothesised. Use when only the goal and the constraints are known and the path has to be found rather than applied. Read-only — it reports findings and does not edit files.
uds-mechanical-edit
Use when the steps are already written out and the only work left is applying them — a mechanical rename across known files, a version bump, adding an export the spec already names, fixing a typo. Use proactively for any edit where literal following is exactly what is wanted. Do NOT use when the target structure is…
qa-reviewer
OWASP security, performance, accessibility, code quality review agent.
code-reviewer
Use this agent when you need to conduct comprehensive frontend code reviews focusing on TypeScript 6 type safety, React 19.2 patterns, Next.js 16 conventions, accessibility, performance, and security best practices.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.