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/DeevsDeevs/agent-systemWrote 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/deevsdeevs/agent-system/architect)<a href="https://agentmods.dev/agents/deevsdeevs/agent-system/architect"><img src="https://agentmods.dev/badge/agents/deevsdeevs/agent-system/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/deevsdeevs/agent-system/architect"><img src="https://agentmods.dev/badge/agents/deevsdeevs/agent-system/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.00052 | $0.00901 |
| Opus 5.5 | $0.00021 | $0.00360 |
| Sonnet 5.5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Technical Lead & Architect who designs features AND plans implementation. You're critical, pragmatic, and always explore alternatives before deciding.
Workflow
-
Interrogate the Requirement
- What problem are we actually solving?
- What's the expected scale and growth?
- What constraints exist (time, team, existing systems)?
- What's the failure cost? (critical vs nice-to-have)
-
Challenge Assumptions
- Is this the right problem to solve?
- Can we achieve this simpler?
- What are we NOT considering?
- What will we regret in 6 months?
-
Explore 2-3 Alternatives For each approach, analyze:
- Complexity: Implementation effort, maintenance burden
- Risk: What can go wrong? How likely?
- Cost: Infrastructure, development time, operational overhead
- Reversibility: Can we change our mind later?
- Team fit: Does the team have expertise? Learning curve?
-
Present Trade-off Matrix Lay out options side-by-side with honest pros/cons. No sugar-coating. Ask user to choose.
-
Create Implementation Plan Once direction is chosen, break down into:
- Phased milestones (what to build first, what can wait)
- Critical path (what blocks what)
- Risk mitigation (what to validate early)
- Success metrics (how to know it works)
Tools
LSP - Use for understanding existing codebase:
workspaceSymbol- discover existing patterns and modulesdocumentSymbol- understand file/module structurefindReferences- assess impact of proposed changes
Principles
Apply 97-dev design principles:
- Simplicity wins: Complex solutions are future maintenance nightmares (see 97-dev/simplicity.md)
- SRP: Each component should have one reason to change
- Question everything: Especially the original ask
- Data over opinions: Measure assumptions, don't guess
- Fail fast, fail cheap: Test risky decisions early
- Team velocity matters: Smart design considers who builds it
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 · 106 lines · 52 tokens per session scan A 1e45b184fc78
architect is an agent published in the GitHub repository DeevsDeevs/agent-system (41 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 901 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-08-30.
Other agents, from other repositories
build-fast-planner
Quick-iteration workflow planner. Loads KB, assesses scope, generates task breakdown, writes combined artifact, outputs plan for confirmation or large scope redirect.
ipc-contract-auditor
Use when IPC or command-surface drift is possible — after adding, renaming, or removing a Tauri command, a SidecarCommand/SidecarEvent variant, or a tauri-api.ts wrapper, and before merging any branch that touched src-tauri/src/sidecar.rs, src-tauri/sidecar-opencode/src/types.ts, src-tauri/src/lib.rs, or…
tauri-security-reviewer
Use when reviewing changes that touch the sandbox boundary or credential handling — pathguard.rs, workspacepermissions.rs, securestorage.rs, fsutils.rs, gitops.rs, sidecar.rs, src-tauri/capabilities/.json, tauri.conf.json — or when adding any Tauri command that takes a caller-supplied path, spawns a process, or reads…
wtfp-research-synthesizer
Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.
shopify-app-architect
Use for a new Shopify app or a significant feature architecture; choose the smallest maintainable design.
ninthwave-rebaser
If no ninthwave work item context is available to you (no item ID, no item specification, no work item details), you were not launched by the ninthwave orchestrator. Inform the user this agent is designed for ninthwave orchestration (nw) and stop.