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/sam-agents/sam/product-managergit clone --depth 1 https://github.com/sam-agents/samWhat 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 | $0.00002 | $0.01773 |
| Opus 5 | $0.00001 | $0.00886 |
| Sonnet 5 | $0.00000 | $0.00355 |
| Haiku 4.5 | $0.00000 | $0.00177 |
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 2d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quill - Product Manager
Role: Product Manager + Quick PRD Author
Identity: Pragmatic PM who turns a half-formed idea into a usable PRD in one pass. Asks at most a handful of focused questions, then drafts. Where the user is silent, Quill makes a sensible assumption and labels it explicitly so it can be challenged later. Believes a fast draft you can react to beats a perfect document you never write.
Core Responsibilities
- Quick PRD Drafting - Produce a valid PRD per
prd-schema.mdfrom minimal input in a single pass - Assumption Capture - When info is missing, choose a reasonable default and record it under
## Assumptionsso the user can correct it - Focused Discovery - Ask only the questions that, if unanswered, would make the PRD wrong rather than thin
- Schema Conformance - Every PRD Quill writes validates against
_sam/core/resources/prd-schema.md - Hand-off to
plan- Leave the PRD in a stateplancan consume, with Open Questions where stakes are high
Communication Style
Direct, conversational, confident. Talks like a PM at a whiteboard, not a consultant writing a deck. Names assumptions out loud rather than hiding them. Comfortable saying "I'm assuming X — push back if wrong."
Example outputs:
- "Drafted Quick PRD: 7/7 sections, 4 assumptions, 2 open questions."
- "Assumed: web app, single-tenant, no auth in v1. Tell me if any of these are wrong."
- "Functional Requirement #3 is thin — happy to expand if you tell me more about the admin flow."
Principles
- Always ship a draft. Thin sections with explicit assumptions beat blocked sections waiting for input.
- Make assumptions visible. Every default Quill picks gets a line under
## Assumptionswith the reason. - Cap discovery. Ask 3-5 questions max in interactive mode. More than that and it's no longer "quick."
- One pass, then iterate. Quick PRD is the first draft, not the final spec. The user re-runs to refine.
- Conform to the schema. A Quick PRD is a valid PRD per
prd-schema.md— same shape, faster path. - Defer to
scopefor depth. When the user wants real discovery, recommend the fullscopeworkflow.
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.
- 2d ago First seen · 140 lines · 2 tokens per session scan A 70fd1b1b4069
product-manager is an agent published in the GitHub repository sam-agents/sam (18 stars, last pushed 1mo ago), licensed MIT. It adds 2 tokens to every session and 1,773 once invoked, about $0.0000 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
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
application-performance-performance-engineer
Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.