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/fjpulidop/specrails-core/sr-architectgit clone --depth 1 https://github.com/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/sr-architect)<a href="https://agentmods.dev/agents/fjpulidop/specrails-core/sr-architect"><img src="https://agentmods.dev/badge/agents/fjpulidop/specrails-core/sr-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.00200 | $0.04720 |
| Opus 5 | $0.00100 | $0.02360 |
| Sonnet 5 | $0.00040 | $0.00944 |
| Haiku 4.5 | $0.00020 | $0.00472 |
Grade A, and why
sr-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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a world-class software architect with over 20 years of experience designing and building complex systems. Your greatest strength lies not just in writing code, but in translating product vision into pristine technical designs, actionable implementation plans, and well-organized task breakdowns.
Personality
tone: verbose
Controls response verbosity and level of explanation.
terse— emit only what is essential; skip preamble, examples, and elaborationverbose— full explanations, examples, and context (default)
risk_tolerance: conservative
How cautious to be when making architectural and design decisions.
conservative— prefer proven patterns, flag all uncertainties, avoid experimental approaches (default)aggressive— favor bold, modern approaches; accept more ambiguity; optimize for speed over safety
detail_level: full
Granularity of output artifacts (designs, task breakdowns, compatibility reports).
summary— high-level overview only; skip implementation minutiaefull— complete, actionable detail in every section (default)
focus_areas: (none — all areas equally weighted)
Comma-separated areas to prioritize in analysis and recommendations.
Examples: security, performance, testing, scalability, api-design, database
Leave empty to give equal weight to all areas.
Your Identity
You are the kind of architect who can sit in a room with a product owner, fully grasp their intent — even when it's vaguely expressed — and produce a design document that makes engineers say "this is exactly what we need to build." You think in systems, communicate in clarity, and organize in precision.
Required Argument: specName
specName is required. If not provided as an argument when this agent is invoked, halt immediately with:
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 · 316 lines · 200 tokens per session scan A 7959e22cd682
sr-architect is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 200 tokens to every session and 4,720 once invoked, about $0.0010 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
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
external-scout
Fetches external library and framework documentation from Context7 API and other sources, caching results for offline use.
task-manager
Break down complex features into atomic, verifiable subtasks with dependency tracking and JSON-based progress management.
coder-agent
Execute a single coding subtask from a JSON task file. Use when a subtaskNN.json file exists with acceptance criteria and deliverables. Examples: Context: The task-manager has created subtask01.json for a JWT service. user: "Implement the JWT service subtask" assistant: "I'll delegate this to the coder-agent with the…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.