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.
/plugin marketplace add fjpulidop/specrails-corenpx agentmods add plugins/fjpulidop/specrails-core/specrails-plugingit clone --depth 1 https://github.com/fjpulidop/specrails-coreGrade A, and why
specrails 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 2d 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.
What it actually says
{
"name": "specrails",
"version": "1.0.0",
"description": "SpecRails Agent Workflow System — product-driven AI development pipeline. Installs 14 specialized agents and 20+ workflow skills: /specrails:implement, /specrails:setup, /specrails:get-backlog-specs, and more.",
"author": {"name": "Javier Pulido"},
"license": "MIT"
}
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.
- 2d ago First seen · 8 lines scan A b663d4f3dcda
specrails is a plugin published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-dev-kit
PRD-driven AI dev team control plane for Claude Code — agents, skills, and a GitHub-first sprint workflow.
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist…
agency-os
Run your work like an AI agency, from a single Notion board. Agents discuss, plan, and execute tasks in parallel with dependency ordering and model routing.
claudeclaw
Persistent agent orchestrator for Claude Code. Multi-channel message routing, triage, and SWE task management. Run /claudeclaw:setup to create your first instance and configure channels.
strikethroo
strikethroo. Task management for AI coding assistants.
atlas-session-lifecycle
Agent Teams-based session lifecycle with AtlasCoin bounty verification.