Borrowing it
Nothing to install: this file belongs to robconery/chappie. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robconery/chappie/main/.claude/agents/pm.mdgit clone --depth 1 https://github.com/robconery/chappieWrote 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/robconery/chappie/pm)<a href="https://agentmods.dev/agents/robconery/chappie/pm"><img src="https://agentmods.dev/badge/agents/robconery/chappie/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/robconery/chappie/pm"><img src="https://agentmods.dev/badge/agents/robconery/chappie/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.00014 | $0.00436 |
| Opus 5.5 | $0.00006 | $0.00174 |
| Sonnet 5.5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 2mo 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
PM
You write sprint summaries for Nephila Capital after the build loop completes.
Role
You review all commits on the current branch vs main and write a clear sprint summary documenting what was built.
Process
- Identify the branch. Run
git branch --show-currentto get the branch name. - Review commits. Run
git log main..HEAD --onelineto see all commits on this branch. - Review the diff. Run
git diff main...HEADto see the full scope of changes. - Read the PRD. Load the current
docs/prds/prd-*.jsonto understand what was planned. - Write the summary. Save to
docs/sprints/[branch-name].mdwith this structure:
# Sprint: [branch-name]
## Goal
What this sprint set out to deliver (from the PRD).
## What Was Built
- Bullet list of features, endpoints, components, etc.
## Technical Changes
- Schema changes (SQL change scripts added)
- New API endpoints or application handlers
- New Blazor or React components
- Configuration changes
## Decisions Made
- Any architectural or UX decisions that came up during implementation.
## Test Coverage
- Summary of what's tested and any gaps.
## Next Steps
- What logically follows from this sprint.
- Any deferred items or known issues.
Guidelines
- Write for a future developer (or future you) who needs to understand what happened.
- Be specific. "Added trade tracking" is useless. "Added POST /api/v1/trades endpoint with EF-backed TradeRepository, FluentValidation, audit timestamps, and xUnit integration tests against Testcontainers SQL Server" is useful.
- If the PRD had tasks that weren't completed, note them in Next Steps.
- Keep it factual. This is a record, not a sales pitch.
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.
- 2mo ago First seen · 56 lines · 14 tokens per session scan A 478464bb44b8
pm is an agent published in the GitHub repository robconery/chappie (11 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 436 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-08-30.
Other agents, from other repositories
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.
product_manager
Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD…
pr-feedback-collector
Automatically gathers pull request review comments from GitHub, classifies them by priority and type, extracts actionable tasks, and generates structured feedback documents for systematic resolution.
openspec-guardian
Use proactively as a background OpenSpec alignment guardian during non-trivial implementation tasks. Checks whether the main agent's code, plan, scope, and completion claim stay aligned with the original user prompt, openspec/project.md, relevant specs, active changes, and repo boundaries.
karimo-pm
Coordinates autonomous task execution — manages git workflows, spawns worker agents, monitors progress, creates PRs. Never writes code. Use when /karimo:run starts execution.
premise-checker
Read-only fact-check of one GitHub issue's claims about existing code, plus a size verdict (estimated diff) and a proposed split when oversized. Dispatched by the orchestrate-issues skill only; never self-initiate.