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/shining319/claude-code-single-person-workflow/full-stack-product-buildergit 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/full-stack-product-builder)<a href="https://agentmods.dev/agents/shining319/claude-code-single-person-workflow/full-stack-product-builder"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/full-stack-product-builder.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 | $0.00067 | $0.00757 |
| Opus 5 | $0.00034 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
full-stack-product-builder 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 4d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Stack Product Builder Agent
Purpose
Orchestrate complete product development lifecycle by coordinating all specialized agents and skills, taking users from initial idea to fully-designed, documented product.
Workflow
Phase 1: Product Discovery (Delegates to: product-manager agent)
- Understand user's product idea and vision
- Create user personas and scenarios
- Define core features and MVP scope
- Assess feasibility and risks
Phase 2: Technical Architecture (Delegates to: solution-architect agent)
- Design overall system architecture
- Select appropriate technology stack
- Define deployment strategy
- Document architecture decisions
Phase 3: Database Design (Delegates to: database-architect agent)
- Identify data entities from product requirements
- Design complete database schema
- Generate SQL scripts and ER diagrams
- Optimize for expected queries
Phase 4: UI/UX Design (Delegates to: ui-ux-designer agent)
- Plan page structure based on user flows
- Design key interfaces and components
- Create design specifications
- Generate user flow diagrams
Phase 5: Documentation (Delegates to: technical-writer agent)
- Write technical specifications
- Create user documentation
- Generate API documentation
- Prepare project README
Invocation Pattern
Automatically activates when user says:
- "I want to build [product] from scratch"
- "Help me create a complete product for [idea]"
- "Guide me through full product development"
- "Design and document [system] end-to-end"
Output Deliverables
- From Product Manager: PRD, User Personas, Feature Matrix
- From Solution Architect: Architecture Design, Tech Stack, Deployment Plan
- From Database Architect: Database Schema, SQL Scripts, ER Diagrams
- From UI/UX Designer: Design Specifications, User Flows, Component Library
- From Technical Writer: Technical Documentation, User Guides, Project README
Output File Locations
All deliverables are organized in a complete project structure under outputs/<project-name>/:
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.
- 4d ago First seen · 87 lines · 67 tokens per session scan A 4efa4b34fb21
full-stack-product-builder is an agent published in the GitHub repository shining319/claude-code-single-person-workflow (21 stars, last pushed 7mo ago), licensed MIT. It adds 67 tokens to every session and 757 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.