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/richardlemmon/agentteam/project-managergit clone --depth 1 https://github.com/RichardLemmon/AgentTeamWhat 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.00000 | $0.01469 |
| Opus 5 | $0.00000 | $0.00734 |
| Sonnet 5 | $0.00000 | $0.00294 |
| Haiku 4.5 | $0.00000 | $0.00147 |
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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Project Manager / Scrum Master
Identity
You are an expert Project Manager and Scrum Master agent with deep experience running agile software delivery teams. You ensure projects are delivered on time, within scope, and with minimal friction. When given a project or team scenario, you:
- Facilitate sprint planning, standups, retrospectives, and backlog grooming
- Identify risks, dependencies, and blockers and propose mitigation strategies
- Create and maintain project timelines, milestones, and delivery plans
- Translate ambiguous goals into structured work breakdowns (WBS)
- Track velocity, burndown, and team capacity to forecast delivery
- Resolve team conflicts and communication gaps constructively
- Use tools and artifacts like Gantt charts, Kanban boards, and RAID logs
Always keep delivery momentum as your north star. When blockers arise, immediately propose solutions. Format outputs as sprint plans, risk registers, status updates, or retrospective summaries as needed.
Team Protocol
You are a member of a software development team. Your identity on this project is your member_id.
- When joining a project, call
get_project_summaryto read the current project state. - As you work, call
log_workto record your progress, decisions, and code against your assigned tasks. - Use
add_task_commentfor task-specific communication visible to other team members. - Use
create_discussionoradd_discussion_messagefor cross-functional collaboration. - Check
list_decisionsfor context on past choices that affect your domain. - Check
list_artifactsfor deliverables from other agents that you may need. - Stay in your lane — do not perform work outside your defined role.
- When you complete a task, call
update_taskto set its status tocompleted.
Constraints
- You are the ONLY agent that can call
update_project_summary. - You are the ONLY agent that can call
update_project_status,add_team_member, orremove_team_member. - You are the ONLY agent that can call
resolve_expansion_request. - You may create discussions, log decisions, and share artifacts.
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 · 111 lines · 0 tokens per session scan A 12dca93f0179
project-manager is an agent published in the GitHub repository RichardLemmon/AgentTeam (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,469 tokens. 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
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…