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 skills/fjpulidop/specrails-core/setupnpx skills add fjpulidop/specrails-core --skill setupgit 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/setup)<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/setup"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/setup.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.00057 | $0.02006 |
| Opus 5 | $0.00028 | $0.01003 |
| Sonnet 5 | $0.00011 | $0.00401 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
setup 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 3d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecRails Setup
Initialize this project with the specrails workflow by generating project-specific configuration files. The sr plugin already provides all agents, skills, and commands — this skill generates the data layer that adapts the workflow to your project.
Input: $ARGUMENTS — optional flags:
--name <name>— project name (defaults to directory name)--stack <stack>— primary tech stack description (e.g. "Next.js + Rails + PostgreSQL")--domain <domain>— product domain (e.g. "SaaS analytics", "developer tooling")--skip-claude-md— skip CLAUDE.md generation
Phase 1: Gather Project Context
If $ARGUMENTS is empty, interactively gather:
- Project name — default: current directory basename
- Tech stack — ask: "What is your primary stack? (e.g. Next.js + Rails, Django + React, Go + gRPC)"
- Domain — ask: "What domain is this product in? (e.g. developer tooling, SaaS analytics, e-commerce)"
- Backend layer — ask: "What are your backend technologies?" (can be same as stack)
- Frontend layer — ask: "What are your frontend technologies?" (can be same as stack)
- CI commands — ask: "What command runs your full CI? (e.g. npm test, make test, ./scripts/ci.sh)"
If --name, --stack, --domain flags are provided, use those values and skip the interactive prompts.
Confirm the gathered values before proceeding:
About to set up specrails for:
Project: <name>
Stack: <stack>
Domain: <domain>
Backend: <backend>
Frontend: <frontend>
CI: <ci_command>
Proceed? [Y/n]
Phase 2: Create Directory Structure
mkdir -p .specrails/personas
mkdir -p .claude/agent-memory/sr-architect
mkdir -p .claude/agent-memory/sr-developer
mkdir -p .claude/agent-memory/sr-reviewer
mkdir -p .claude/agent-memory/sr-product-manager
mkdir -p .claude/agent-memory/sr-product-analyst
mkdir -p .claude/agent-memory/sr-test-writer
mkdir -p .claude/agent-memory/sr-doc-sync
mkdir -p .claude/agent-memory/sr-merge-resolver
mkdir -p .claude/agent-memory/sr-security-reviewer
mkdir -p .claude/agent-memory/sr-backend-developer
mkdir -p .claude/agent-memory/sr-frontend-developer
mkdir -p .claude/agent-memory/sr-backend-reviewer
mkdir -p .claude/agent-memory/sr-frontend-reviewer
mkdir -p .claude/agent-memory/sr-performance-reviewer
mkdir -p .claude/agent-memory/explanations
mkdir -p .claude/agent-memory/failures
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.
- 3d ago First seen · 277 lines · 57 tokens per session scan A 78781809ce68
setup is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,006 once invoked, about $0.0003 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 skills, from other repositories
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…
scientific-critical-thinking
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.