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 instructions/slbug/claude-ruby-grape-rails/claude-mdgit clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/instructions/slbug/claude-ruby-grape-rails/claude-md)<a href="https://agentmods.dev/instructions/slbug/claude-ruby-grape-rails/claude-md"><img src="https://agentmods.dev/badge/instructions/slbug/claude-ruby-grape-rails/claude-md.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.02165 | $0.02165 |
| Opus 5 | $0.01082 | $0.01082 |
| Sonnet 5 | $0.00433 | $0.00433 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
claude-ruby-grape-rails CLAUDE.md 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Development Guide
Ruby/Rails/Grape Claude Code plugin. Validated on macOS, Linux, WSL. Native Windows unsupported.
Posture
- Lean read-only specialist agents (
omitClaudeMd: true) - Fast
SessionStartwith async refresh - Filesystem is the state machine — each phase reads previous phase's output
- Targeted post-edit routing via
rubyish-post-edit.shfan-out - Solutions feed back into future cycles
Workflow
/rb:brainstorm (optional) -> /rb:plan -> /rb:work -> /rb:verify -> /rb:review -> /rb:compound
| | | | |
v v v v v
.claude/plans/{slug}/ (namespace) (namespace) (namespace) .claude/solutions/
Commands
| Command | Phase | Input | Output |
|---|---|---|---|
/rb:brainstorm |
Discovery | Topic / feature idea | .claude/plans/{slug}/interview.md |
/rb:plan |
Planning | Feature description | .claude/plans/{slug}/plan.md |
/rb:plan --existing |
Enhancement | Plan file | Enhanced plan with research |
/rb:brief |
Understanding | Plan file | Interactive walkthrough (ephemeral) |
/rb:work |
Execution | Plan file | Updated checkboxes + .claude/plans/{slug}/progress.md |
/rb:verify |
Verification | [--quick|--full] (resolves from current branch state, NOT plan path) |
Verification results |
/rb:review |
Quality | Changed files | .claude/reviews/{review-slug}-{datesuffix}.md + per-agent artifacts |
/rb:compound |
Knowledge | Solved problem | .claude/solutions/{category}/{fix}.md |
/rb:full |
All | Feature description | Complete cycle with compounding |
Artifact Directories
| Namespace | Path |
|---|---|
| Plan | .claude/plans/{slug}/{plan.md, research/, progress.md, scratchpad.md} |
| Review consolidated | .claude/reviews/{review-slug}-{datesuffix}.md |
| Review per-agent | .claude/reviews/{agent-slug}/{review-slug}-{datesuffix}.md |
| Review manifest | .claude/reviews/{review-slug}/RUN-CURRENT.json + RUN-HISTORY.jsonl (schema: references/run-manifest.md) |
| Audit | .claude/audit/ |
| Cross-plan research consolidated | .claude/research/{topic-slug}.md |
| Cross-plan research per-aspect | .claude/research/{topic-slug}/{aspect-slug}.md |
| Research manifest | .claude/research-fanout/{topic-slug}/RUN-CURRENT.json + RUN-HISTORY.jsonl |
| Investigations | .claude/investigations/{agent}/{slug}-{datesuffix}.md |
| Skill metrics | .claude/skill-metrics/ |
| Solutions | .claude/solutions/{category}/ |
| Provenance scans | .claude/provenance-scan/ |
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 · 225 lines · 2,165 tokens per session scan A 366a9120e120
claude-ruby-grape-rails CLAUDE.md is an instructions file published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 4d ago), licensed MIT. It adds 2,165 tokens to every session, about $0.0108 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 instructions, from other repositories
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.