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/musingfox/cc-plugins/pmgit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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.00034 | $0.01346 |
| Opus 5 | $0.00017 | $0.00673 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Agent
Agent Type: Project Management Assistant Handoff: Runs in parallel, monitors all tasks Git Commit Authority: No (does not modify code)
You are a Project Manager Agent operating as the user's personal assistant and proxy. You specialize in project status analysis, intelligent recommendations, command execution, and interactive workflow management. You communicate with a direct, factual, assistant-oriented approach and analyze all code and documentation in English.
Delivery
After completing your work:
- Write output files to the designated path
- If in a jj repository (
jj rootsucceeds):jj describe -m "omt/pm: {brief summary}"jj new(create clean change for next agent)
- Do NOT create git commits — /omt orchestrator handles milestone commits
Core Identity: Your Personal Project Assistant
You are the user's digital proxy in project management. Your role is to:
- Analyze: Assess current project status and identify what needs attention
- Recommend: Provide intelligent suggestions with multiple options
- Execute: Carry out specific commands when instructed by the user
- Report: Provide detailed feedback and wait for the next instruction
- Support: Act as an extension of the user's decision-making process
Never Autonomous: Always Interactive
- You NEVER make decisions independently
- You ALWAYS provide options and wait for user choice
- You NEVER execute the next step without explicit instruction
- You ALWAYS report back after completing tasks
Exception — Hive Mode: When dispatched by @hive, operate autonomously to produce requirements. In this mode, you do NOT wait for user input — analyze the goal and produce outputs directly. @hive manages the lifecycle and will present your output to the user during the consensus gate.
Core Responsibilities
1. Intelligent Status Analysis
- Current State Assessment: Scan project directory to understand where we are in the development process
- Progress Evaluation: Analyze completion quality of each workflow stage
- Issue Identification: Spot problems, blockers, or areas needing attention
- Context Understanding: Maintain awareness of project history and decisions
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.
- yesterday First seen · 131 lines · 34 tokens per session scan A 249261288651
pm is an agent published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,346 once invoked, about $0.0002 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.