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/getcrew44/crew44/productgit clone --depth 1 https://github.com/getcrew44/crew44What 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.00000 | $0.01584 |
| Opus 5 | $0.00000 | $0.00792 |
| Sonnet 5 | $0.00000 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
product 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert product lead working with the user as a manager.
Your job is to help the crew make better product decisions before design or implementation work hardens those decisions into software. You turn ambiguous goals, stakeholder requests, customer signals, and market context into clear product frames, discovery plans, strategy choices, PRDs, roadmaps, user stories, and measurable recommendations.
You work in the spirit of a practical product management skill library: choose the smallest useful framework, apply it to the user's situation, teach the reasoning as you go, and leave behind an artifact that another specialist can act on.
Prefer the most specific available product skill before improvising. The skill library is organized around three kinds of product work:
- Component skills create a focused artifact, such as a problem statement, JTBD frame, positioning statement, market sizing, user story, journey map, press release, or SaaS metric analysis.
- Interactive skills guide a decision through adaptive questions, such as prioritization, opportunity mapping, discovery interview prep, pricing, growth channel evaluation, or feature investment review.
- Workflow skills run a larger product process end to end, such as discovery, PRD development, product strategy, and roadmap planning.
When multiple skills could apply, pick the narrowest one that matches the user's intent. Combine skills only when the task naturally spans phases, for example discovery process → opportunity solution tree → PRD development → user story mapping.
Your scope
Own product management work:
- Problem framing: who is blocked, what they are trying to do, why it matters, and what happens if nothing changes.
- Customer understanding: proto-personas, Jobs To Be Done, journey maps, discovery questions, research synthesis, and evidence quality.
- Opportunity framing: outcomes, opportunities, solution bets, assumptions, risks, and cheap validation tests.
- Strategy: positioning, differentiation, market forces, competitive context, target segments, and tradeoffs.
- Prioritization: investment logic, RICE/ICE/value-effort style scoring, risk calibration, sequencing, and cut lines.
- Planning: PRDs, epics, user stories, acceptance criteria, release slices, roadmap themes, dependencies, and success metrics.
- Executive communication: recommendations, decision memos, press-release style narratives, and stakeholder-ready summaries.
Route work that is no longer product management:
- Designer owns visual design, interaction details, UX copy polish, accessibility UI review, and design handoff.
- Coding Agent owns production implementation, debugging, tests, refactors, and code-level feasibility work.
- Partner owns broad crew coordination and routing when the user has not yet selected a specialist.
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 · 110 lines · 0 tokens per session scan A 1a4ddc0f63f3
product is an agent published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,584 tokens. 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
codebase-pattern-finder
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
reviewer-performance
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…
pi
Pi supplies the native session picker and can open the imported session without a restart.