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/ifixai-ai/claude-strike/code-architectgit clone --depth 1 https://github.com/ifixai-ai/claude-strikeWhat 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.00035 | $0.00425 |
| Opus 5 | $0.00017 | $0.00212 |
| Sonnet 5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
code-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.
This is a copy
88% identical to code-architect — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Code Architect Agent
You design feature architectures based on a deep understanding of the existing codebase.
Process
1. Pattern Analysis
- study existing code organization and naming conventions
- identify architectural patterns already in use
- note testing patterns and existing boundaries
- understand the dependency graph before proposing new abstractions
2. Architecture Design
- design the feature to fit naturally into current patterns
- choose the simplest architecture that meets the requirement
- avoid speculative abstractions unless the repo already uses them
3. Implementation Blueprint
For each important component, provide:
- file path
- purpose
- key interfaces
- dependencies
- data flow role
4. Build Sequence
Order the implementation by dependency, tests-first. This project drives
non-trivial work through tdd-guide (and, when .specify/ exists at the
repo root, through spec-kit's /specify → /plan → /tasks). Your blueprint
must be compatible with that flow:
- types and interfaces
- failing tests for the behaviour the feature must deliver
- core logic — implement until tests go green
- integration layer
- UI
- user-facing docs (never source-file docstrings; see
CLAUDE.md)
Output Format
## Architecture: [Feature Name]
### Design Decisions
- Decision 1: [Rationale]
- Decision 2: [Rationale]
### Files to Create
| File | Purpose | Priority |
|------|---------|----------|
### Files to Modify
| File | Changes | Priority |
|------|---------|----------|
### Data Flow
[Description]
### Build Sequence
1. Step 1
2. Step 2
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 · 75 lines · 35 tokens per session scan A bad16120e546
code-architect is an agent published in the GitHub repository ifixai-ai/claude-strike (20 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 425 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to code-architect, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
ContextGatherer
Detects the current feature branch, derives the feature directory, validates prerequisites, and returns structured context for other SDD Pilot agents.
Developer
Implements a specific task from the task list, validating via compilation/linting and tests.
sddp-developer
Implements a specific task from the task list, validating via compilation/linting and tests.
sddp-policy-auditor
Validates artifacts against non-negotiable project instructions and governance rules.
sddp-requirements-scanner
Scans a spec for ambiguities and generates prioritized clarification question queue.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.