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 skills add pranav8494/team-of-agents --skill project-managergit clone --depth 1 https://github.com/pranav8494/team-of-agentsWrote 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/skills/pranav8494/team-of-agents/project-manager)<a href="https://agentmods.dev/skills/pranav8494/team-of-agents/project-manager"><img src="https://agentmods.dev/badge/skills/pranav8494/team-of-agents/project-manager/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/skills/pranav8494/team-of-agents/project-manager"><img src="https://agentmods.dev/badge/skills/pranav8494/team-of-agents/project-manager.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.00056 | $0.02036 |
| Opus 5 | $0.00028 | $0.01018 |
| Sonnet 5 | $0.00011 | $0.00407 |
| Haiku 4.5 | $0.00006 | $0.00204 |
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 12d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
Iron Law
Surface blockers two sprints before they land, not the day they hit.
Every task without an owner and a due date will not get done.
Scope is the only variable you can reliably control, when things slip, negotiate scope, not deadlines.
Before Taking Any Action
- Announce the artefact you're creating (sprint plan, RAID log, status report, etc.) and the project context
- Confirm scope, what time horizon, which team, what's already known about the work
- Ask for confirmation before creating or updating any files or trackers
- Report what was produced and what decisions or inputs are still needed from stakeholders
Task Approach
Use this table to determine what to produce for each task type:
| User asks for | What to produce |
|---|---|
| Sprint plan | Sprint goal statement + backlog items selected with owners + capacity check + dependency flags for anything that could block the sprint |
| RAID log | Populated RAID log using the structure below; all four sections filled with probability/impact ratings, owners, and due dates |
| Status report | RAG-flagged report using the standard format: summary, this week, next week, blockers/decisions needed, RAID updates |
| Risk identification | Risk register entries with probability × impact matrix; mitigation action per risk; owner and review date |
| Dependency map | Table of internal and external dependencies with due dates, owners, and On Track / At Risk / Blocked status |
| Retrospective | Completed retro in the chosen format (Start/Stop/Continue, 4Ls, or blameless postmortem); every action item has an owner and due date |
| Critical path analysis | Task list with dependency links, duration estimates, identified critical path, and monitoring schedule |
| Escalation write-up | Structured escalation note: issue, impact, decision needed, recommendation, decision deadline |
| Ceremony design / facilitation notes | Agenda with time-boxes, inputs required, expected outputs, and facilitation prompts for each ceremony |
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.
- 12d ago First seen · 210 lines · 56 tokens per session scan A bb64cb241fa3
project-manager is a skill published in the GitHub repository pranav8494/team-of-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,036 once invoked, about $0.0003 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 skills, from other repositories
tasks
Turn an approved SPEC.md into a complete TASKS.md (phases, parallel tracks, dependency map), then create matching GitHub issues, a GitHub Project board, and empty-directory scaffolding from the spec's package layout. Use whenever the user invokes /ank:tasks, says "break this into tasks", "create the issues", "wire up…
wayfinder
Chart a too-big effort as a shared map of decision tickets on the Gaia headquarters issue tracker, then resolve them one at a time until the way to the destination is clear. Use when someone says: "this is too big for one session", "chart a map", "wayfinder map", "plan this effort", "what do we need to decide first"…
gaia-triage
Triage the Gaia issue backlog and skill-batch intake queue. Use this skill when someone asks to: "triage issues", "clean up the issue tracker", "review the backlog", "close stale issues", "process the intake queue", "review skill-batches", "evaluate draft skill proposals", "approve or reject pending skills", "is this…
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).