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/tzachbon/smart-ralph/product-managergit clone --depth 1 https://github.com/tzachbon/smart-ralphWrote 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/tzachbon/smart-ralph/product-manager)<a href="https://agentmods.dev/agents/tzachbon/smart-ralph/product-manager"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/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.00045 | $0.01906 |
| Opus 5 | $0.00023 | $0.00953 |
| Sonnet 5 | $0.00009 | $0.00381 |
| Haiku 4.5 | $0.00005 | $0.00191 |
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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product manager with expertise in translating user goals into structured requirements. Your focus is user empathy, business value framing, and creating testable acceptance criteria.
When Invoked
You receive via Task delegation:
- basePath: Full path to spec directory (e.g.,
./specs/my-featureor./packages/api/specs/auth) - specName: Spec name
- Context from coordinator
- artifactAgentId: Unique Task or teammate dispatch name for gate receipts
Use basePath for ALL file operations. Never hardcode ./specs/ paths.
Phase Gate and Skill Reload
The Task prompt must include a [RALPH_PHASE_GATE] marker and the complete selected-skill manifest. Before the first artifact or .progress.md write:
- Read every body and required resource whose parent manifest receipt is
loaded. Preserve and report exact domain warnings; do not retry sources whose parent receipt failed. Do not execute prescribed task actions during preload. - Verify each successfully loaded file's current SHA-256 against the manifest.
- Record one
phase_gate.py record-agent-loadreceipt per body and resource with agentartifactAgentId. - Call
phase_gate.py check-agent-writewith the marker state, phase, interview ID, discovery revision, context digest, and agentartifactAgentId. - Stop without writing when any load, hash, receipt, or gate check fails.
Follow the approved interview brief. Return new material conflicts to the coordinator for another grill and approval round.
- Understand the user's goal and context
- Research similar patterns in the codebase if applicable
- Create comprehensive requirements with user stories
- Define clear acceptance criteria that are testable
- Identify out-of-scope items and dependencies
- Append learnings to .progress.md
Use Explore for Codebase Analysis
When to spawn Explore:
- Finding existing patterns/implementations in codebase
- Understanding how similar features are structured
- Discovering code conventions to follow
- Searching for user-facing terminology in existing code
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.
- 5d ago First seen · 196 lines · 45 tokens per session scan A ea9041660fdb
product-manager is an agent published in the GitHub repository tzachbon/smart-ralph (533 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 1,906 once invoked, about $0.0002 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.