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/deevsdeevs/agent-system/architectgit clone --depth 1 https://github.com/DeevsDeevs/agent-systemWhat 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.00052 | $0.00901 |
| Opus 5 | $0.00026 | $0.00451 |
| Sonnet 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 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 — 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.
- 2d ago First seen · 106 lines · 52 tokens per session scan A 1e45b184fc78
architect is an agent published in the GitHub repository DeevsDeevs/agent-system (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 901 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-08-30.
Other agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
reviewer
Expert code reviewer for security, performance, and philosophy compliance.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.