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 doctorgit 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/doctor)<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/doctor"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/doctor/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/doctor"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/doctor.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.00040 | $0.01446 |
| Opus 5 | $0.00020 | $0.00723 |
| Sonnet 5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
doctor 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 9d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecRails Doctor
Run a full diagnostic check on the sr plugin installation and project configuration. Outputs a health report that identifies missing components, misconfigured files, and actionable fixes.
Input: $ARGUMENTS — optional:
--fix— automatically fix issues where possible (safe fixes only: create missing dirs, initialize empty config files)--verbose— show detailed output for each check
Check 1: Plugin agents
Verify that all expected plugin agents are accessible. The sr plugin should provide 14 agents:
Expected agents: sr:architect, sr:developer, sr:reviewer, sr:backend-developer, sr:frontend-developer, sr:backend-reviewer, sr:frontend-reviewer, sr:security-reviewer, sr:performance-reviewer, sr:test-writer, sr:doc-sync, sr:merge-resolver, sr:product-manager, sr:product-analyst
Check: Read the plugin's agent definitions to confirm they're installed.
Result: PASS if all agents found, WARN if some missing.
Check 2: Required tools
Check for required CLI tools:
which git && git --version
which openspec && openspec --version 2>/dev/null || echo "MISSING"
which gh && gh --version 2>/dev/null || echo "NOT_INSTALLED (optional)"
which npm && npm --version 2>/dev/null || echo "NOT_INSTALLED (optional)"
git— requiredopenspec— required for OpenSpec workflow (/specrails:opsx:*skills)gh— required only ifBACKLOG_PROVIDER=githubnpm— required only if project uses Node.js
Check 3: Project configuration
Check for .specrails/config.yaml:
- If missing:
WARN— run/specrails:setupto create it - If exists: parse and validate required fields (
project.name,stack.description,ci.command) - Flag any fields with placeholder values like
"<STACK>"or"<CI_COMMAND>"
Check for .specrails/backlog-config.json:
- If missing:
WARN— run/specrails:setupto create it - If exists: validate
BACKLOG_PROVIDERis one ofgithub,local,none
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.
- 9d ago First seen · 147 lines · 40 tokens per session scan A 5352acbbe898
doctor is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,446 once invoked, about $0.0002 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
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
memstack-development-performance-audit
Use this skill when the user says 'performance audit', 'why is it slow', 'optimize performance', 'page speed', 'Core Web Vitals', 'lighthouse', 'load time', or needs to diagnose and fix frontend or backend performance issues. Do NOT use for code reviews or security audits.
semgrep-rule-creator
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
variant-analysis
Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.