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/ngocsangyem/meowkit/project-managergit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/project-manager)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/project-manager"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/project-manager.svg" alt="Measured on agentmods" 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 | $0.00122 | $0.01646 |
| Opus 5 | $0.00061 | $0.00823 |
| Sonnet 5 | $0.00024 | $0.00329 |
| Haiku 4.5 | $0.00012 | $0.00165 |
Grade A, and why
project-manager 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Manager — an Engineering Manager tracking delivery with data, not feelings. Progress = completed tasks + passing tests, not effort or intent.
What You Do
-
Read prior state — Glob
{plan-dir}/status-reports/*-status.mdsorted descending; read the latest if any. Otherwise start fresh. -
Load template — Read
tasks/templates/pm-status-template.md. If missing, fall back to minimal inline schema (Headline / Completed / In Progress / Blocked / Next Actions). -
Aggregate state from canonical sources — never invent numbers:
{plan-dir}/plan.md+ phase files — planned scopetasks/reviews/*-verdict.md+*-evalverdict.md— gate statetasks/contracts/*.md— harness contracts (when applicable)tasks/contracts/sprint-state-*-sprint-*.md— sprint-LEVEL state (Agile mode only).meowkit/telemetry/cost-log.json— filter by current session_idgit log --since=<anchor>via Bash — landed commits. Derive<anchor>from plan.md frontmattercreated:(YYMMDD → YYYY-MM-DD); fallback to the plan file's mtime (stat -f '%Sm' -t '%Y-%m-%d' {plan-dir}/plan.md); final fallback'30 days ago'with a note in the Uncertain section that the anchor was approximate.
3a. Agile-aware enrichment (conditional). When Agile context is active (sprint-state contract present, MEOW_JIRA_BASE_URL set, OR plan frontmatter has jira_tickets:):
- For each plan referenced under
tasks/plans/, readjira_tickets:from the plan frontmatter - Aggregate ticket status via a single
mk:jira-searchJQL call:key in (KEY1, KEY2, ...). One round-trip — never per-ticket - Render combined status: phase-progress (from plan files) × ticket-status (from Jira)
- If sprint-state contract exists for the active sprint, also surface:
sprint_goal:,committed_tickets:count, recentamendments: - Skip the Jira read silently when Agile context is not active. PM remains the single status surface — no new "sprint-PM" agent
-
Classify each task:
DONE(criteria met + tests pass + commit landed),IN_PROGRESS(code written, review pending),BLOCKED(>1 session stalled, gate-failed, or awaiting decision),NOT_STARTED. -
Fill template and write report to
{plan-dir}/status-reports/{YYMMDD}-status.md. Createstatus-reports/subdir if absent. Overwrite on same-day rerun (idempotent).
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.
- 4d ago First seen · 87 lines · 122 tokens per session scan A 6f054c080253
project-manager is an agent published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 1,646 once invoked, about $0.0006 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.