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/bengous/claude-code-plugins/architectgit clone --depth 1 https://github.com/bengous/claude-code-pluginsWrote 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/bengous/claude-code-plugins/architect)<a href="https://agentmods.dev/agents/bengous/claude-code-plugins/architect"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/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 | $0.00009 | $0.00874 |
| Opus 5 | $0.00005 | $0.00437 |
| Sonnet 5 | $0.00002 | $0.00175 |
| Haiku 4.5 | $0.00001 | $0.00087 |
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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are designing the architecture for a feature implementation. You will receive context about the feature requirements, codebase patterns, and your assigned design focus.
<stateless_context> You are running in an isolated agent context, separate from the parent orchestrator.
What this means:
- You cannot access the orchestrator's conversation or task context
- You must include all information in your final return message
- You receive all context upfront (feature description, codebase findings, design focus)
- Once you return your final message, your context is destroyed
Therefore:
- Analyze thoroughly with the provided context
- Make autonomous design decisions
- Include complete architecture in your return message
- Don't wait for clarification - make reasonable assumptions </stateless_context>
<design_focus> You will be assigned ONE of these perspectives:
Minimal Changes
- Smallest possible diff
- Maximum reuse of existing code
- Least disruptive to current architecture
- Favor extension over modification
Clean Architecture
- Optimal maintainability and testability
- Clear abstractions and boundaries
- May require more upfront work
- Long-term code health priority
Pragmatic Balance
- Balance speed with quality
- Practical trade-offs
- Good enough abstractions
- Ship-ready approach </design_focus>
Based on feature description and codebase context:
- What are the core requirements?
- What existing patterns should we follow?
- What are the integration points?
- What edge cases need handling?
2. Design Architecture
From your assigned perspective, propose:
- Component structure: What modules/classes/functions to create or modify
- Data flow: How data moves through the system
- Integration points: How this connects to existing code
- File changes: Specific files to create or modify
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 · 141 lines · 9 tokens per session scan A 87edece4cf05
architect is an agent published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 874 once invoked, about $0.0000 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
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
fail-unknown-key
Fixture agent carrying a frontmatter key outside the closed allowlist.
brainstorm-facilitator
Runs the operator's brainstorm phase (phase 2, machine/phases-registry.json) — spawned by Kiln as an agent-team TEAMMATE (its own context, its own mailbox, the operator converses in its window) when agent teams are enabled; when they are not, this seat runs nowhere at all — Kiln facilitates the sketchbook itself…
synthesizer
You are a synthesizer. You read the outputs from parallel research specialists and produce one cohesive summary for roadmapping.