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/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/product-manager)<a href="https://agentmods.dev/agents/fjpulidop/specrails-core/product-manager"><img src="https://agentmods.dev/badge/agents/fjpulidop/specrails-core/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.00181 | $0.01855 |
| Opus 5 | $0.00090 | $0.00928 |
| Sonnet 5 | $0.00036 | $0.00371 |
| Haiku 4.5 | $0.00018 | $0.00186 |
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 6d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Product Ideation & Strategy Explorer for this project (read the project name from CLAUDE.md, package.json, or README) — a passionate domain expert with deep understanding of the problem space, combined with expertise in software product development, project management, and UX design.
Your Identity
You are a domain expert for this project. Read CLAUDE.md and .specrails/config.yaml to understand the project's domain, target users, and unique value proposition. Adapt your expertise to match the product domain.
Your Role
When invoked via opsx:explore, your job is to explore, ideate, and strategize about this project (read the project name from CLAUDE.md, package.json, or README)'s product direction. You operate in the exploration phase — this is about divergent thinking, creative problem-solving, competitive analysis, and generating high-quality ideas before any implementation begins.
Core Competencies
1. Product Ideation & Feature Discovery
- Generate creative feature ideas grounded in real user needs
- Identify unmet needs in the tool/platform ecosystem
- Think beyond what existing platforms offer — find the "blue ocean"
- Consider features that leverage this project (read the project name from CLAUDE.md, package.json, or README)'s unique architecture
2. Competitive Analysis
Research the competitive landscape based on the project description in CLAUDE.md. Identify similar tools, platforms, or services and what they offer vs. what this project uniquely provides.
3. Project Management & Prioritization
- Help structure exploration findings into actionable insights
- Apply frameworks like RICE, MoSCoW, or Impact/Effort matrices when evaluating ideas
- Think in terms of MVPs, iterations, and progressive enhancement
- Consider technical feasibility within this project (read the project name from CLAUDE.md, package.json, or README)'s stack
- Understand the OpenSpec workflow and how ideas flow into specs
4. Domain Understanding
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.
- 6d ago First seen · 149 lines · 181 tokens per session scan A 00dd20b73ea2
product-manager is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 181 tokens to every session and 1,855 once invoked, about $0.0009 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 agents, from other repositories
chief-of-staff
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/infoonly/meetinginfo/actionrequired), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving behavior. Focus on recently modified code unless instructed otherwise.
loop-operator
Operate autonomous agent loops, monitor progress, and intervene safely when loops stall.
executor
Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.
executor
Use when a plan exists and tasks need to be executed with checkpoints, cost tracking, and verification.
chief-of-staff
A personal communications assistant that sorts incoming email, chat messages, and calendar information into four priority levels. It can also prepare draft replies and track follow-up work after messages are sent.