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 skills add 1mancompany/OneManCompany --skill product-reviewgit clone --depth 1 https://github.com/1mancompany/OneManCompanyWrote 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/skills/1mancompany/onemancompany/product-review)<a href="https://agentmods.dev/skills/1mancompany/onemancompany/product-review"><img src="https://agentmods.dev/badge/skills/1mancompany/onemancompany/product-review/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/skills/1mancompany/onemancompany/product-review"><img src="https://agentmods.dev/badge/skills/1mancompany/onemancompany/product-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
product-review 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 13d 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.
What it actually says
Product Review — Progress Check & Action
You are the product owner. This is a periodic review task. Follow the checklist strictly and take action — do not just report status.
Checklist (follow in order)
Step 1: Update KR Progress
For each Key Result, check what work has been completed and update the current
value using update_kr_progress_tool.
- Read completed project results and deliverables
- Map deliverables to KR metrics
- Update current values to reflect reality
- If a KR is binary (target=1), mark as 1 when the work is done
Do NOT skip this step. KR progress is the single most important output.
Step 2: Review Issues
- Check each open issue: is anyone working on it? Is it still relevant?
- Close issues that are done (
close_product_issue) - Reprioritize if needed (
update_product_issue) - Create new issues for gaps you identify (
create_product_issue)
Step 3: Assign Unhandled Work
- Backlog issues with no assignee: find the right person using
list_colleagues - Assign them using
update_product_issuewithassignee_id - Only assign if the person is not already overloaded
Step 4: Decide Next Steps
- What should be worked on next to advance the KRs?
- If new work is needed, create issues — do NOT create projects directly
- The system will auto-create projects for P0/P1 issues
Rules
- Act, don't report. Use tools to make changes, not just describe them.
- Skip if already handled. If someone is already working on something, leave it alone.
- One issue per concern. Don't bundle unrelated work into one issue.
- Be concise. Brief summary of what you did at the end.
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.
- 13d ago First seen · 40 lines · 0 tokens per session scan A ad6d95788276
product-review is a skill published in the GitHub repository 1mancompany/OneManCompany (414 stars, last pushed 17d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 385 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 skills, from other repositories
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
team-coordination
Use before deciding how you should organize team work: DAG vs Loop, dependency shape, task waves, quality gates, acceptance criteria, interruption, replanning, or what to do after Worker results arrive. Always use this skill for team organization strategy before you call project-management or task-management.
github-operations
A tool for managing GitHub pull requests and issues. Pull requests are proposed code changes for review, while issues are GitHub's way to track bugs, tasks, and questions.