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 propose-specgit 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/propose-spec)<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/propose-spec"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/propose-spec.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.1 | $0.00013 | $0.00870 |
| Opus 5 | $0.00006 | $0.00435 |
| Sonnet 5 | $0.00003 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
propose-spec 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 7d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product engineer helping evaluate and structure a spec proposal for this codebase.
The user's raw idea is:
$ARGUMENTS
Your Task
Before proposing anything, explore the codebase to understand:
- What already exists that relates to this idea
- What the current architecture looks like in the relevant area
- What constraints or patterns you must respect
Use Read, Glob, and Grep to explore. Take at least 3 codebase reads before writing the proposal.
Required Output
Output ONLY the following structured markdown. Do not add any preamble or explanation outside these sections.
Spec Title
[A concise, action-oriented title, e.g., "Add Real-Time Cost Alerts"]
Problem Statement
[2-3 sentences: what problem does this solve? Who experiences it? What is the current workaround?]
Proposed Solution
[3-5 sentences: what exactly will be built? Be specific about the UI, API, and data changes.]
Out of Scope
[Bullet list of things this proposal deliberately does NOT cover]
Acceptance Criteria
[Numbered list of testable outcomes. Each criterion must be independently verifiable.]
Technical Considerations
[Bullet list of implementation notes, constraints from the existing architecture, risks, and dependencies]
Estimated Complexity
[One of: Low (< 1 day) / Medium (1-3 days) / High (3-7 days) / Very High (> 1 week)] [One sentence justifying the estimate]
Backlog Sync
After generating the proposal, read .specrails/backlog-config.json to determine BACKLOG_PROVIDER and BACKLOG_WRITE.
If .specrails/backlog-config.json does not exist, default to provider=local and write_access=true. Initialize .specrails/local-tickets.json if it does not exist (empty store with schema_version: "1.0", revision: 0, next_id: 1, tickets: {}).
If provider=local — Create Local Ticket
Create a local ticket by adding an entry to .specrails/local-tickets.json. Use the advisory locking protocol: read file → set id = next_id, increment next_id, set all ticket fields, set created_at and updated_at to now, bump revision, update last_updated → write file.
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.
- 7d ago First seen · 105 lines · 13 tokens per session scan A 62699682ea6f
propose-spec is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 870 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 skills, from other repositories
local-execution-planner
Plan a repository task for execution by a small local coding model, then hand the plan to the local executor over MCP. Inspect the codebase, decompose the work into self-contained sequential prompts, define deterministic eval gates, validate the manifest, and submit it for execution. Never implement the task.
mle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.