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/coco-research/cocoWrote 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/coco-research/coco/pm-advisor)<a href="https://agentmods.dev/agents/coco-research/coco/pm-advisor"><img src="https://agentmods.dev/badge/agents/coco-research/coco/pm-advisor/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/coco-research/coco/pm-advisor"><img src="https://agentmods.dev/badge/agents/coco-research/coco/pm-advisor.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.00063 | $0.01710 |
| Opus 5.5 | $0.00025 | $0.00684 |
| Sonnet 5.5 | $0.00013 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
pm-advisor 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 Changed · +3 lines 8de2436567c4
- 1mo ago First seen · 204 lines · 63 tokens per session scan A 2ffb3972c360
pm-advisor is an agent published in the GitHub repository coco-research/coco (704 stars, last pushed yesterday), with no licence file. It adds 63 tokens to every session and 1,710 once invoked, about $0.0003 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-manager
Keeps the project organized, on schedule, and within budget — tracks progress against the plan, surfaces risks, and owns the delivery timeline.
scrum-master
Facilitates the team's process, removes roadblocks, and keeps the collaboration loop healthy — the team's process conscience.
product-owner
Represents the customer, owns the work backlog, and decides what features get built first. The voice of the customer inside the team.
planner
Turns an intent into committed intent.md, spec.md, and plan.md. Use for a new feature or capability that needs requirements before code. Loads discovery plus the Superpowers brainstorming and writing-plans skills. Writes no implementation code.
rig-architect
Tech lead agent for planning, architecture decisions, and ticket creation. Use when breaking down a feature, designing a solution, evaluating tradeoffs, or creating implementation tickets. Invoke before coding begins on any non-trivial change.
sw-change-owner
The sole owner of one specwright change dispatched by a delivery: runs the change ladder end to end in its own branch and worktree, records the decisions it took, and reports shipped or blocked back to the delivery orchestrator.