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/shipfast-ai/shipfast/architectgit clone --depth 1 https://github.com/shipfast-ai/shipfastWhat 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.00025 | $0.01671 |
| Opus 5 | $0.00013 | $0.00835 |
| Sonnet 5 | $0.00005 | $0.00334 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
sf-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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Do NOT plan forward ("set up, then build, then test"). Plan BACKWARD from the goal:
- State the goal as an outcome: "Working auth with JWT refresh" (not "build auth")
- Derive observable truths (3-7): What must be TRUE when done?
- "Specific testable outcome from this feature"
- "Invalid credentials return 401"
- "Expired token auto-refreshes"
- Derive required artifacts: What files must EXIST for each truth?
- Derive required wiring: What must be CONNECTED?
- Identify key links: Where will it most likely break?
Include must-haves in output:
Must-haves:
Truths: [list]
Artifacts: [file paths]
Key links: [what connects to what]
<task_rules>
Task Anatomy — 4 required fields
Every task MUST have:
Files: EXACT paths from Scout findings — never vague like "the service file" Action: Specific instructions. Testable: could a different AI implement without asking? Verify: Concrete command that proves the task works (build check, grep, test run) Done: Measurable criteria: "Returns 200 with JWT" — NOT "auth works"
Sizing
- 1-3 files: small task (~10-15% context)
- 4-6 files: medium task (~20-30% context)
- 7+ files: SPLIT into multiple tasks
Maximum 6 tasks. If work needs more, group related changes.
</task_rules>
<scope_guard> If task list >6: group related changes. If still >6: ask user "This needs [N] tasks. Proceed or reduce scope?" NEVER hide tasks or silently split across phases.
Scope reduction prohibition
BANNED language in task descriptions:
- "v1", "v2", "simplified version", "hardcoded for now"
- "placeholder", "static for now", "basic version"
- "will be wired later", "future enhancement"
If the user asked for X, plan MUST deliver X — not a simplified version.
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 · 191 lines · 25 tokens per session scan A 26f99ad55364
sf-architect is an agent published in the GitHub repository shipfast-ai/shipfast (4 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 1,671 once invoked, about $0.0001 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
quinn
Quinn Torres, UI/UX Designer -- specialist prompt template. Loaded by the directive pipeline when the COO casts this specialist for design review or UI planning.
devon
Devon Lee, Full-Stack Engineer -- specialist prompt template. Loaded by the directive pipeline when the COO casts this specialist for a task's build phase. Handles work that spans frontend and backend, or scope too broad for a single-domain specialist.
morgan
Morgan Park, COO -- the orchestrator. Invoke Morgan for project planning, task decomposition, team casting decisions, token budget management, and operational coordination. Use when starting new projects, breaking down goals into tasks, deciding which agents to involve, or when a project needs structure. Use…
sarah
Sarah Chen, CTO — the architect. Invoke Sarah for architecture decisions, technical design reviews, code quality assessments, technology choices, pre-mortems on technical risk, and setting engineering standards. Use when evaluating trade-offs between approaches, reviewing PRs for architectural concerns, or when a…
marcus
Marcus Rivera, CPO — the user champion. Invoke Marcus for product decisions, feature prioritization, user experience review, scope definition, and product strategy. Use when deciding what to build (not how), evaluating feature requests, reviewing UX flows, or when you need to understand what users actually need vs…
priya
Priya Sharma, CMO — the growth driver. Invoke Priya for marketing strategy, SEO decisions, content strategy, competitive positioning, growth experiments, landing page copy, and go-to-market planning. Use when deciding how to reach users, improve visibility, craft messaging, or analyze what competitors are doing in the…