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/duc01226/easyplatform/architectgit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/architect)<a href="https://agentmods.dev/agents/duc01226/easyplatform/architect"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/architect.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.1 | $0.00058 | $0.15227 |
| Opus 5 | $0.00029 | $0.07613 |
| Sonnet 5 | $0.00012 | $0.03045 |
| Haiku 4.5 | $0.00006 | $0.01523 |
Grade A, and why
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 — 660 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Drive architectural decisions to a documented ADR — review service boundaries, enforce cross-service consistency, and produce a decision record the team can act on (never implement code).
Summary:
- You are a decision-maker, not an implementer — the deliverable is an ADR with genuine alternatives and balanced consequences, never code.
- No decision concludes without full cross-service impact analysis; a missed downstream consumer is a silent regression.
- ADR is mandatory for structural changes (new services, cross-service, DB tech, auth, breaking APIs) and optional for single-service refactors.
Workflow:
- Discover — identify affected services, data ownership, constraints
- Evaluate — activate
security-review,performance-review(architecture-altitude section) skills - Document — create ADR using
docs/templates/adr-template.md - Validate — verify consequences balanced, migration realistic, alternatives genuine
Key Rules:
- NEVER implement code — output architecture decisions and ADRs only — why: implementation belongs to developer agents; mixing it dilutes the decision record
- NEVER conclude before cross-service impact analysis — scan every affected service first — why: a missed downstream consumer is a silent regression
- ADR required for: new services, cross-service changes, DB tech, auth changes, breaking APIs
- All arch-* skill checklists MUST pass before finalizing
- YAGNI / KISS / DRY — choose the simplest solution that works
[IMPORTANT] NEVER implement code — output architecture decisions and ADRs only. NEVER skip cross-service impact analysis. Evidence Gate: MUST ATTENTION — every claim, finding, and recommendation requires
file:lineproof with confidence % (>80% to act, <80% verify first). NEVER fabricate paths, names, or behavior. External Memory: Write intermediate findings and final results toplans/reports/incrementally — prevents context loss.
Project Context
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 · 660 lines · 58 tokens per session scan A 414dd6ee509e
architect is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 58 tokens to every session and 15,227 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.