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/tody-agent/codymasterWrote 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/tody-agent/codymaster/pm)<a href="https://agentmods.dev/agents/tody-agent/codymaster/pm"><img src="https://agentmods.dev/badge/agents/tody-agent/codymaster/pm/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/tody-agent/codymaster/pm"><img src="https://agentmods.dev/badge/agents/tody-agent/codymaster/pm.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.00026 | $0.00341 |
| Opus 5.5 | $0.00010 | $0.00136 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
pm 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 41 lines · 26 tokens per session scan A 714e51e0100b
pm is an agent published in the GitHub repository tody-agent/codymaster (54 stars, last pushed 1mo ago), with no licence file. It adds 26 tokens to every session and 341 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
producer
The Producer manages all production concerns: sprint planning, milestone tracking, risk management, scope negotiation, and cross-department coordination. This is the primary coordination agent. Use this agent when work needs to be planned, tracked, prioritized, or when multiple departments need to synchronize.
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
product-manager
The Product Manager owns the product roadmap, user requirements, PRDs, user stories, and the bridge between business goals and technical implementation. Use this agent when defining features, prioritizing the backlog, writing acceptance criteria, analyzing user needs, or aligning stakeholders on what to build and why.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
jira-bulk
Execute bulk JIRA operations on 10+ issues via the jira-as CLI wrapper: bulk transition, assign, set-priority, clone, delete. Dry-run is MANDATORY first. Routed by mk:jira-bulk skill. NOT for single-issue ops (jira-issue / jira-lifecycle); NOT for bulk-update by JQL field changes (jira-search bulk-update — same…
jira-jsm
Execute JIRA Service Management operations via the jira-as CLI wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains, 45 verbs total). Routed by mk:jira-jsm skill. Requires JSM-licensed tenant + agent or admin role. NOT for core Jira issue ops (jira-issue)…