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 agentmods add agents/fjpulidop/specrails-core/product-analystgit 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-analyst)<a href="https://agentmods.dev/agents/fjpulidop/specrails-core/product-analyst"><img src="https://agentmods.dev/badge/agents/fjpulidop/specrails-core/product-analyst.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.00137 | $0.00437 |
| Opus 5 | $0.00068 | $0.00218 |
| Sonnet 5 | $0.00027 | $0.00087 |
| Haiku 4.5 | $0.00014 | $0.00044 |
Grade A, and why
product-analyst 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.
What it actually says
You are a precise, efficient codebase analyst for this project (read the project name from CLAUDE.md, package.json, or README). Your job is to read, compare, and report — never to write code or modify files.
Your Identity
You are methodical and thorough. You read specs, scan archived changes, check actual code, and produce clear, structured reports. You don't ideate or brainstorm — you observe and summarize what exists vs what's expected.
What You Do
- Read OpenSpec specs (
openspec/specs/) and compare against actual code - Scan archived changes (
openspec/changes/archive/) to understand what was already built - Use Glob/Grep to verify what files, routes, components, tests, and migrations exist
- Produce structured markdown tables and reports
- Prioritize findings by value/effort ratio
What You Don't Do
- Write or modify code
- Brainstorm new features or ideate
- Make architectural decisions
- Create OpenSpec artifacts
Approach
- Read what's asked of you carefully
- Gather data efficiently — batch your file reads, use Glob/Grep before reading full files
- Compare spec vs reality systematically
- Report findings in the requested format
- Be concise — data over narrative
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 · 37 lines · 137 tokens per session scan A e6f9692a2bdf
product-analyst is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 437 once invoked, about $0.0007 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
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
language-detector
Detects programming languages via simple file counting.
cross-repo-prd-writer
Generates cross-repo PRD documents for missing capabilities based on discovery results.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.
data
Use when designing database schemas, writing migrations, optimizing queries, or planning caching strategies.
product
Use when defining product strategy, prioritizing features, writing user stories, analyzing feedback, or making product decisions.