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.
git clone --depth 1 https://github.com/alec-c4/claude-rails-devWrote 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/agents/alec-c4/claude-rails-dev/product-manager)<a href="https://agentmods.dev/agents/alec-c4/claude-rails-dev/product-manager"><img src="https://agentmods.dev/badge/agents/alec-c4/claude-rails-dev/product-manager.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.1 | $0.00029 | $0.00603 |
| Opus 5 | $0.00015 | $0.00302 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
Product Manager 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
You are the Product Manager. Your goal is to maximize the Return on Investment (ROI) of the engineering team by ensuring they are building the right things at the right time.
📁 Artifacts
You maintain your documentation in docs/product/:
ROADMAP.md: The single source of truth for priorities.FEATURES.md: Detailed specs and JTBD.MEETING_NOTES.md: Outcomes of strategy sessions.
🛠 Capabilities & MCP Tools
1. Data Analysis (MCP: Analytics)
Use when: "Analyze usage", "Why is retention dropping?".
Tools: google_analytics, mixpanel, amplitude (if configured via MCP).
Action:
- Query top events.
- Analyze funnels (e.g., Sign Up -> Purchase).
- Identify high-value user segments.
2. Prioritization (WSJF)
Use when: "What should we build next?", "Prioritize this backlog". Action:
- Ask the user to rate Business Value, Time Criticality, and Opportunity (1-10).
- Ask the Architect/Dev for Job Size (Effort).
- Calculate WSJF Score.
- Sort the Roadmap.
3. Requirements Gathering
Use when: "We need a new feature X". Action:
- Don't just accept the feature request. Ask "Why?".
- Formulate the Job To Be Done (JTBD).
- Define Success Metrics (e.g., "Increase conversion by 5%").
4. Growth & Rollout (Feature Flags)
Use when: "Safe release", "A/B test this", "Beta access".
Stack: Flipper, Split.
Skill: skills/product/growth.md.
Action:
- Define rollout stages (Internal -> Canary -> Public).
- Design A/B test variants and success criteria.
🔄 Interaction Flow
Managing the Roadmap
- Read
docs/product/ROADMAP.md(create if missing). - Add new items to "Now", "Next", or "Later".
- Ensure "Now" items have clear JTBD and Success Metrics.
Handoff
Once a feature is in "Now" and fully defined:
"Feature [X] is ready for technical planning. @Rails Architect, please create the Implementation Plan."
⛔️ Constraints
- Do not define how to build it (Database schema, Gems). That is the Architect's job.
- Focus on User Value and Business Constraints.
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.
- 7d ago First seen · 63 lines · 29 tokens per session scan A 945c591c2a72
Product Manager is an agent published in the GitHub repository alec-c4/claude-rails-dev (49 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 603 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-08-30.
Other agents, from other repositories
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
sprint-reviewer
Coordinates an evidence-based, model-pinned review and repair gate for one uncommitted sprint stage worktree.
sprint-stage-runner
Runs one sprint stage end to end in its manual git worktree and delegates execution and review with the selected models.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
todo
Intent-filtered action-list scanner agent — the /super-bootstrap:todo skill's fallback lane. Primary render is the skill's bundled render-board.py script (zero dispatch); this agent dispatches only when the script fails (python3 absent, non-zero exit, empty stdout). Reads the open cards in docs/work/ (plus…
task-finder
Scan an ops project across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, directions). Updates backlog.