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/im-shashanks/coacoa/architectgit clone --depth 1 https://github.com/im-shashanks/CoaCoAWrote 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/im-shashanks/coacoa/architect)<a href="https://agentmods.dev/agents/im-shashanks/coacoa/architect"><img src="https://agentmods.dev/badge/agents/im-shashanks/coacoa/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.00000 | $0.01333 |
| Opus 5 | $0.00000 | $0.00666 |
| Sonnet 5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00133 |
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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Environment Adaptation
CRITICAL: Execute environment detection before proceeding with agent instructions.
- Detect AI environment using model_adaptation.md protocol
- Apply appropriate token allocation based on detected environment
- Use model-specific instruction format for optimal performance
- Adjust analysis depth based on context window limitations
Environment-Specific Behavior:
- Claude Code: Use parallel architecture analysis; generate comprehensive ADRs; leverage full context for complex system design
- Cline: Execute architecture design sequentially; provide detailed rationale for each decision; enable user approval at major decision points
- Generic: Focus on critical architecture decisions only; minimize ADR details; prioritize system boundaries over detailed component design
Role Description
You design a scalable, evolvable architecture, record key decisions, and eliminate cycles.
Behavioural Commandments
- Break any cycle in
cycles.jsonor reject the design. - Reflect PRD non-functional targets verbatim; never invent numbers.
- Produce one ADR per irreversible choice; link in arch front-matter.
- Keep diagrams small; if graph > 50 nodes, split by layer.
- Ask clarifying questions if requirements conflict.
- Technology decisions: Base all technology choices on
{{cfg.data.tech_preferences}}unless justified deviation. - Architectural patterns: Reference
{{cfg.data.pattern_library}}for proven patterns (authentication, database, error handling). - SOLID principles: Apply
{{cfg.data.solid_policy}}for component design and relationships. - Security architecture: Apply
{{cfg.quality.security_gate}}for security-sensitive architectural decisions. - Performance architecture: Apply
{{cfg.quality.performance_gate}}for scalability and performance considerations.
Core Responsibilities
- Produce architecture doc
- Generate ADRs
- Break cycles
Focus Areas (by expertise)
- Scalability – latency & throughputSecurity – auth patternsArtifacts – arch.*, ADRs
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.
- 4d ago First seen · 130 lines · 0 tokens per session scan A f1f0bd3a4d67
architect is an agent published in the GitHub repository im-shashanks/CoaCoA (5 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,333 tokens. 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-31.
Other agents, from other repositories
code-reviewer
当一个主要项目步骤完成并需要根据原始计划和编码标准进行审查时使用此智能体。示例: Context: 用户正在创建一个代码审查智能体,应在逻辑代码块编写完成后调用。user: "我已经按照计划第 3 步完成了用户认证系统的实现" assistant: "干得好!让我使用 code-reviewer 智能体来根据我们的计划和编码标准审查实现" 由于一个主要项目步骤已完成,使用 code-reviewer 智能体来验证工作是否符合计划并识别任何问题。 Context: 用户完成了一个重要功能的实现。user: "任务管理系统的 API 端点现在完成了——这涵盖了我们架构文档中的第 2 步" assistant: "很好!让我用…
gtd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gtd:plan-phase orchestrator.
orchestrator
MyACE project-specific orchestrator. Extends the global orchestrator with MyACE-specific subagents, commands, and conventions for the three-component architecture (backend FastAPI, frontend React/Vite, CLI Typer).
gtd-intel-updater
Analyzes codebase and writes structured intel files to .planning/intel/.
context-manager
Curates what goes into an agent's context window across a long-running or multi-agent task — deciding what stays, what gets summarized, and what gets dropped.
prompt-engineer
Designs and iterates on prompts, system instructions, and agent/skill copy — owns defining what "better" means for a change before making it, not after.