Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slbug/claude-ruby-grape-rails/plugin install 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/skills/slbug/claude-ruby-grape-rails/full)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/full"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/full/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/slbug/claude-ruby-grape-rails/full"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/full.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.00092 | $0.01201 |
| Opus 5.5 | $0.00037 | $0.00480 |
| Sonnet 5.5 | $0.00018 | $0.00240 |
| Haiku 4.5 | $0.00009 | $0.00120 |
Grade A, and why
rb:full 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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Workflow
/rb:full runs the full plan-work-verify-review-compound cycle autonomously.
Skill body owns the complete cycle from main session.
STEP 0: Read the cycle + state-machine references
Read ${CLAUDE_SKILL_DIR}/references/cycle-patterns.md and
${CLAUDE_SKILL_DIR}/references/state-machine.md. Apply the state
transitions, blocker handling, and recovery protocols as the
canonical procedure. Each child skill (/rb:plan, /rb:work,
/rb:verify, /rb:review, /rb:compound) runs its own STEP 0
playbook read on entry.
Cycle
/rb:brainstorm(optional) → if requirements vague/rb:plan→ reuses pre-bound namespace; produces plan.md via main-session research fanout/rb:work→ executes plan tasks; clears active-plan marker on completion/rb:verify→ runs full verification stack (no plan-path arg; resolves from current branch)/rb:review→ main-session review fanout (no plan-path arg; resolves from diff)/rb:compound→ captures learnings; accepts plan path arg
Use /rb:full for well-scoped work where the user wants the full cycle.
Skip for vague requirements or trivial fixes.
State Machine (summary)
INITIALIZING → [DISCOVERING] → PLANNING → WORKING → VERIFYING → REVIEWING → COMPOUNDING → COMPLETED
DISCOVERING is optional (/rb:brainstorm). INITIALIZING transitions
directly to PLANNING when brainstorm is skipped. Branch rules:
${CLAUDE_SKILL_DIR}/references/state-machine.md § "Phase Transitions".
/rb:full skill body writes **State**: to progress.md at every
transition. The plan-stop-reminder.sh hook checks for this field to
skip the manual plan-presentation reminder during autonomous runs.
PLAN_DIR Tracking
- Derive
PLAN_DIRonce at INITIALIZING; track as local variable through the cycle. - Use PLAN_DIR for skill-body's own progress.md State writes only.
- Do NOT pass PLAN_DIR as CLI arg to
/rb:verifyor/rb:review. - Do pass
${PLAN_DIR}/plan.mdto/rb:compound. - After
/rb:workclears the active-plan marker, continue using local PLAN_DIR. Do NOT re-read the marker mid-cycle.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 106 lines · 92 tokens per session scan A 8cb5d1535f0c
rb:full is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 16d ago), licensed MIT. It adds 92 tokens to every session and 1,201 once invoked, about $0.0004 per session on Opus 5.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
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
testunit-skill
Generates Test::Unit tests in Ruby. Classic xUnit-style testing with assert methods and test case classes. Use when user mentions "Test::Unit", "assertequal Ruby", "Ruby test-unit". Triggers on: "Test::Unit", "Ruby test-unit", "assertequal Ruby" (not RSpec).
rspec
RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.
ruby
Ruby development guidelines covering idiomatic code style, Ruby 3.x features, testing with RSpec, and best practices for building maintainable Ruby applications.
python-pytest-ops
Modern pytest patterns for effective testing.