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 Shoebtamboli/rails_claude_skills --skill plan-featuregit clone --depth 1 https://github.com/Shoebtamboli/rails_claude_skillsWrote 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/shoebtamboli/rails_claude_skills/plan-feature)<a href="https://agentmods.dev/skills/shoebtamboli/rails_claude_skills/plan-feature"><img src="https://agentmods.dev/badge/skills/shoebtamboli/rails_claude_skills/plan-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/shoebtamboli/rails_claude_skills/plan-feature"><img src="https://agentmods.dev/badge/skills/shoebtamboli/rails_claude_skills/plan-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.00054 | $0.01660 |
| Opus 5 | $0.00027 | $0.00830 |
| Sonnet 5 | $0.00011 | $0.00332 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
plan-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 11d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Feature Skill
Systematically gather requirements and create implementation plans before starting Rails feature development. Ensures thorough planning, proper task breakdown, and alignment with project conventions.
When to Use This Skill
Use this skill when:
- User mentions planning a new feature
- Starting development on a new capability
- Breaking down complex requirements
- User says "plan", "requirements", "tasks", "kickoff"
- Beginning work on authentication, CRUD, dashboards, or APIs
Instructions
Follow these steps systematically when planning a feature:
Step 1: Understand the Feature Request
Acknowledge the feature request and restate it to confirm understanding:
I'll help you plan the implementation of [feature name]. Let me gather requirements and analyze the codebase to create a structured plan.
Step 2: Gather Requirements
Use the AskUserQuestion tool to ask 2-4 focused questions tailored to the feature type.
For Authentication/Authorization:
- Authentication method (email/password, OAuth, magic links)
- Session management and duration
- Password requirements and reset flow
- Multi-factor authentication needed?
- Role-based access control requirements
For CRUD Features (Posts, Comments, etc.):
- Required fields and validations
- Relationships to existing models
- Permission levels (who can create/edit/delete)
- UI requirements (forms, listings, filters)
- Real-time updates needed?
For Dashboard/Admin Features:
- Metrics and data to display
- Filters and search requirements
- Export capabilities
- Access restrictions
- Update frequency (real-time vs static)
General Questions (always relevant):
- Target users (all users, admins, specific roles)
- Mobile responsiveness requirements
- Performance considerations
- Integration with existing features
Step 3: Analyze Codebase
Use Read, Grep, and Glob tools to understand current state:
# Check existing models
Glob: "app/models/**/*.rb"
# Find similar features
Grep: Search for related functionality
# Review routes
Read: "config/routes.rb"
# Check migrations
Glob: "db/migrate/**/*.rb"
# Review test structure
Glob: "test/**/*_test.rb"
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.
- 11d ago First seen · 254 lines · 54 tokens per session scan A 25e0d9433b01
plan-feature is a skill published in the GitHub repository Shoebtamboli/rails_claude_skills (16 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,660 once invoked, about $0.0003 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-30.
Other skills, from other repositories
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".