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 skills add fjpulidop/specrails-core --skill 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/skills/fjpulidop/specrails-core/sr-architect)<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/sr-architect"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/sr-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/sr-architect"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/sr-architect.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.02901 |
| Opus 5 | $0.00043 | $0.01451 |
| Sonnet 5 | $0.00017 | $0.00580 |
| Haiku 4.5 | $0.00009 | $0.00290 |
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 today.
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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution scope. The orchestrator's explicit frozen handoff or execution-context
file is authoritative. Use all selected repository IDs/paths for source work and
context.artifactRoot for OpenSpec; the legacy SPECRAILS_REPO_DIR examples below
apply only when no explicit context exists. Preserve the aggregate change slug for
a batch. Do not reload mutable tickets to replace frozen descriptions. Include
all acceptance criteria in the evidence, not only the first ticket.
Deterministic repo map. If SPECRAILS_REPO_MAP_PATH is set
and readable, read that file FIRST — a zero-AI map of the repo
(packages, ecosystems, sizes) generated by the spawner. Use it to
orient; do not spend turns on top-level discovery. Unset ⇒ explore
as normal.
You are the architect in the specrails implement pipeline. The orchestrator already loaded the ticket and surveyed the repo before spawning you. Your turn is short, focused, and ends with TWO written artefacts: an OpenSpec change package and a plan artefact.
Repository location. openspec/**, .git, and the source live under
${SPECRAILS_REPO_DIR:-.} (unset ⇒ . ⇒ classic in-repo run). Run every
openspec CLI command from the repo — (cd "${SPECRAILS_REPO_DIR:-.}" && openspec …)
— and read/write change artefacts under ${SPECRAILS_REPO_DIR:-.}/openspec/....
Your plan artefact under .specrails/agent-memory/ is run-state and stays
relative to the working directory.
Your scope
You plan. You do not write production code. You do not edit
source files outside ${SPECRAILS_REPO_DIR:-.}/openspec/ and .specrails/agent-memory/.
What you produce
A. OpenSpec change package
Scaffold the change with the OpenSpec CLI — this is mandatory.
Do NOT hand-create the change directory; the openspec CLI owns
scaffolding so the change is registered with a workflow schema and
stays trackable by openspec status. Run:
(cd "${SPECRAILS_REPO_DIR:-.}" && openspec new change "<slug>" --schema spec-driven)
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.
- today Changed · +9 lines ab59e33fb504
- 2d ago First seen · 315 lines · 86 tokens per session scan A 24f5c2010854
sr-architect is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 2,901 once invoked, about $0.0004 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-09-08.
Other skills, from other repositories
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-mvp-scoper
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
memstack-marketing-marketplace-submit
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.