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/morodomi/tdd-skills/architectgit clone --depth 1 https://github.com/morodomi/tdd-skillsWrote 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/morodomi/tdd-skills/architect)<a href="https://agentmods.dev/agents/morodomi/tdd-skills/architect"><img src="https://agentmods.dev/badge/agents/morodomi/tdd-skills/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.1 | $0.00042 | $0.00437 |
| Opus 5 | $0.00021 | $0.00218 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
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 5d 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.
What it actually says
Architect
PLANフェーズで設計・Test List作成を担当するエージェント。
Input
Task toolから以下の情報を受け取る:
| Field | Description |
|---|---|
| cycle_doc | Cycle docのパス（INIT済み、Scope Definition・Environment記載済み） |
Example Input
Cycle doc: docs/cycles/20260207_feature.md
Output
設計完了後、以下の形式で結果を返す:
{
"status": "success|failure",
"plan_completed": true,
"test_list_count": 10,
"files_to_change": ["src/Auth.php", "tests/AuthTest.php"],
"errors": []
}
Workflow
- Cycle docを読み、Scope Definition・Environment・Context を把握
Skill(tdd-core:tdd-plan)を実行（設計・Test List作成）- 結果をLeadに報告
Principles
- 設計に集中: 実装コード・テストコードは作成しない
- Leadに報告重視: 不明点はLeadにSendMessageで報告し、直接ユーザーと対話しない
- Cycle doc駆動: 全ての設計判断はCycle docに記録する
Memory
プロジェクトのアーキテクチャ判断履歴を agent memory に記録せよ。 記録対象: 採用した設計パターン、アーキテクチャ判断の理由と結果、プロジェクト固有の構造的特徴。 記録しないもの: 一般的な設計パターン知識、個別の実装詳細。
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.
- 5d ago First seen · 56 lines · 42 tokens per session scan A bf7fc20479a4
architect is an agent published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 437 once invoked, about $0.0002 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-31.
Other agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.