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 hoblin/claude-ruby-marketplace --skill featuregit clone --depth 1 https://github.com/hoblin/claude-ruby-marketplaceWrote 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/hoblin/claude-ruby-marketplace/feature)<a href="https://agentmods.dev/skills/hoblin/claude-ruby-marketplace/feature"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/feature/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/hoblin/claude-ruby-marketplace/feature"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/feature.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.00025 | $0.01006 |
| Opus 5 | $0.00013 | $0.00503 |
| Sonnet 5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
feature 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input Format
/rpi:feature <FEATURE_DESCRIPTION> [additional instructions]
- FEATURE_DESCRIPTION: issue URL or plain description (required)
- additional instructions (optional): constraints, focus areas, or any custom guidance
Examples:
/rpi:feature https://linear.app/team/ENG-1234
/rpi:feature ENG-1234 the SpaceshipLauncher class must inherit from BaseVehicle
Context
Create and complete a new feature or chore for this project, from branch creation to PR readiness. Input can be an issue URL or a plain description.
With issue URL: Extract ID, fetch ticket details. With description only: Create new issue in the appropriate project.
Pass any additional instructions from user input through to all subagents and apply them during implementation.
Workflow
Step 1: Setup
Pull latest base branch (usually main or master)
Create feature branch: <type>/<issue-id>-<short-description> (e.g., feature/eng-1234-add-api-endpoint)
Update the ticket: assign to "me", change status to "In Progress"
Step 2: Gather Historical Context
Spawn rpi:thoughts-analyzer with ticket reference, title, description, acceptance criteria, and any additional instructions from user input.
DO NOT proceed to Step 3 until this subagent returns. Its output is required input for Step 3.
Step 3: Research Codebase
After Step 2 completes, spawn research subagents in parallel, passing ticket info, historical context output from Step 2, and any additional instructions from user input:
rpi:codebase-pattern-finder - find similar implementations to model after
rpi:codebase-analyzer - analyze the area being modified
Wait for both subagents to complete before proceeding.
Step 4: Implementation
Activate the rpi:document-code skill before modifying any file.
Follow Rails best practices, CLAUDE.md, and any additional instructions from user input.
Keep code clean and DRY.
When modifying code: fix lurking bugs, refactor, add missing tests and regression tests.
Ensure solid RSpec coverage with well-documented business logic (viewable with --format documentation).
Review changes for completeness.
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.
- yesterday First seen · 116 lines · 25 tokens per session scan A 93da47bcfb8e
feature is a skill published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,006 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-09-07.
Other skills, from other repositories
wrap-up
End-of-session handler that first checks whether the current session's plan is actually complete. If complete: run a quick retrospective, emit a forward-looking follow-up prompt, and — in a git repository — refresh the repo and clean gone branches. If incomplete: skip cleanup and emit ready-to-paste resume prompts so…
workspace-standards
Use when setting up or managing multi-repo workspaces.
omh-github-issue-intake
This is a Hermes-native github-issue-intake workflow skill.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.