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/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/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/bengous/claude-code-plugins/architect"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/architect.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.00009 | $0.00560 |
| Opus 5.5 | $0.00004 | $0.00224 |
| Sonnet 5.5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
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 — 96 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 run in an isolated context: you cannot see the orchestrator's conversation or ask it questions, so everything you know comes from your prompt and the codebase. Where the prompt leaves a choice open, make a reasonable assumption, record it under Key Decisions, and proceed. </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>
<return_format> Return your architecture proposal in this format:
## Architecture Proposal: [Your Focus]
### Summary
[2-3 sentences describing your approach]
### Component Design
- [Component 1]: [Purpose and responsibility]
- [Component 2]: [Purpose and responsibility]
- ...
### File Changes
**Create:**
- `path/to/new/file.ts` - [Purpose]
**Modify:**
- `path/to/existing/file.ts` - [What changes]
### Data Flow
[Describe how data moves through the system]
### Integration Points
- [How this connects to existing system]
### Trade-offs
**Pros:**
- [Benefit 1]
- [Benefit 2]
**Cons:**
- [Drawback 1]
- [Drawback 2]
**Effort:** [Low/Medium/High]
### Key Decisions
- [Important design decision 1 and rationale]
- [Important design decision 2 and rationale]
</return_format>
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 Changed · -7 lines a2ae1acc8850
- 26d ago Changed · -38 lines b03b8338dc1b
- 1mo ago First seen · 141 lines · 9 tokens per session scan A 87edece4cf05
architect is an agent published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 560 once invoked, about $0.0000 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
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.
i18n
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
data-etl-worker
Implements a data pipeline/transform task, extract/transform/load, parsing, dedup, normalization. Write-capable; prefers DuckDB SQL for the transform per the house stack. Dispatched by /kit:execute as the builder when role-classify.sh agent-for names it for the data-etl domain.
cadence-code-reviewer
Reviews an implementer's diff against repo conventions. One of two review stages; runs concurrently with cadence-spec-reviewer on the same diff. Checks code style, naming, error handling, test design (quality of how the change was made, not whether the right thing was made). A finding that contradicts the task spec…
workflow-orchestrator
Expert workflow orchestrator specializing in complex process design, state machine implementation, and business process automation. Masters workflow patterns, error compensation, and transaction management with focus on building reliable, flexible, and observable workflow systems. For per-request task planning use…