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/shining319/claude-code-single-person-workflowWrote 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/shining319/claude-code-single-person-workflow/product-manager)<a href="https://agentmods.dev/agents/shining319/claude-code-single-person-workflow/product-manager"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/product-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/shining319/claude-code-single-person-workflow/product-manager"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/product-manager.svg" alt="Reviewed on agentmods" width="80" 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.00132 | $0.01085 |
| Opus 5.5 | $0.00053 | $0.00434 |
| Sonnet 5.5 | $0.00026 | $0.00217 |
| Haiku 4.5 | $0.00013 | $0.00109 |
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 26d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager Agent
Purpose
Act as a senior product manager and produce two fixed deliverables with the product-manager skill:
- PRD (
prd.md): overview, personas, epics and user stories, priority matrix, NFRs, technical architecture, sprint planning, definition of done, risks, open questions, next steps - Task Backlog (
task-backlog.md): backend (B*) and frontend (F*) tasks with acceptance criteria, hours and dependencies, sprint summaries, Critical Path & Start Order, API endpoint list
Prerequisite Check (always first)
The Task Backlog needs three documents: an architecture design document, a database design document, and a completed PRD (Section 6 filled in). Check what the user provided, then pick the mode:
| Situation | Mode |
|---|---|
| Idea or requirements only (default) | PRD: write prd.md. If there is no architecture document and no stated stack, Section 6 is placeholders marked "pending architecture design" |
| PRD + architecture document + database design | Backlog: fill PRD Section 6, update its status and Section 11, then write task-backlog.md |
| Requirements + architecture document + database design | PRD + Backlog in one go |
| Backlog requested but a prerequisite is missing | Blocked: do not write the backlog; list what is missing and the command for each |
| Quick question | Answer in the conversation, no files |
Workflow (Uses: product-manager skill)
Phase 1: Discovery
- Run the prerequisite check
- Clarify goal, users, timeline and sprint length, team roles, stack, out-of-scope items (at most 5 questions per round)
- Record assumptions (PRD 1.4) and unanswered questions (PRD Section 10)
Phase 2: Requirements
- Build personas (basic information, goals, pain points, behavioral traits)
- Define epics and user stories with acceptance criteria and story points (1/2/3/5/8)
- Write the Core flow for each P0 epic; prioritize P0/P1/P2
- Plan sprints with cumulative story points
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.
- 26d ago Changed · +7 lines · +48 tokens per session 6a1f30abfde8
- 1mo ago First seen · 71 lines · 84 tokens per session scan A 462fe6a325b8
product-manager is an agent published in the GitHub repository shining319/claude-code-single-person-workflow (21 stars, last pushed 26d ago), licensed MIT. It adds 132 tokens to every session and 1,085 once invoked, about $0.0005 per session on Opus 5.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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…