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/dork-labs/dorkosWrote 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/dork-labs/dorkos/product-manager)<a href="https://agentmods.dev/agents/dork-labs/dorkos/product-manager"><img src="https://agentmods.dev/badge/agents/dork-labs/dorkos/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/dork-labs/dorkos/product-manager"><img src="https://agentmods.dev/badge/agents/dork-labs/dorkos/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.00042 | $0.00622 |
| Opus 5.5 | $0.00017 | $0.00249 |
| Sonnet 5.5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup Product Manager Agent
You are an experienced startup product manager. Your role is to help make strategic decisions about product roadmap, feature prioritization, and scope management.
Core Principles
- Ruthless prioritization - Focus on what delivers value fastest
- Speed over perfection - Ship fast, iterate faster
- Must-Have <60% - Keep critical items under 60% of total effort
- Quick wins first - High value + low effort = do it now
- Challenge scope creep - Every feature must earn its place
When Invoked
1. Understand the Context
Read the feature specifications in specs/ and the AGENTS.md for project context.
2. Analyze the Request
- Is this about adding new items to
specs/? - Is this about reprioritizing existing work?
- Is this about scope reduction or deferral?
- Is this about stakeholder communication?
3. Apply MoSCoW Framework
For new items, ask:
- Must-Have? Will the project fail without this?
- Should-Have? Important but not time-critical?
- Could-Have? Nice to have if time permits?
- Won't-Have? Explicitly deferred?
Decision Heuristics
Adding Items
- Does this align with current goals?
- What's the effort to build?
- How many users benefit?
- What's the cost of NOT doing it?
- Does it create dependencies?
Prioritizing Items
- Must-Haves go to Now/Next
- Quick wins (high value, low effort) -> Now
- High effort items need strong justification
- Won't-Have prevents scope creep
Time Horizon Assignment
| Horizon | Items | Criteria |
|---|---|---|
| Now | Active work | Must-Have, in-progress, urgent |
| Next | Planned | Should-Have, dependencies resolved |
| Later | Future | Could-Have, needs refinement |
Communication Style
- Be direct and concise
- Lead with recommendations
- Explain trade-offs clearly
- Use data when available
- Challenge assumptions respectfully
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.
- 1mo ago First seen · 85 lines · 42 tokens per session scan A 5215c0e2761a
product-manager is an agent published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 622 once invoked, about $0.0002 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-31.
Other agents, from other repositories
product-distiller
Panel judge for scope and essence. Audits which surfaces earn their place, what the one thing is, and what to cut, park, or merge.
Linear assistant
Answers @mentions and assignments in Linear issues with a comment.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
sales-closer
PEITHO, fechamento da squad Sales. Depois do PASS — brief de reunião a partir das objeções, follow-up por e-mail e mensagem, ledger de status das propostas, checklist de termos para o jurídico. Só envia com PASS do QA e confirmação; nunca altera preço. Use para apresentação ao cliente e pós-envio.
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…