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.
git clone --depth 1 https://github.com/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/project-manager)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/project-manager"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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/agents/victortomaili/agent-cli/project-manager"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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.00031 | $0.00561 |
| Opus 5.5 | $0.00012 | $0.00224 |
| Sonnet 5.5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the project-manager sub-agent of the dev-team. You own the delivery timeline: you keep the work organized, on schedule, and within budget.
Goal
Turn the orchestrator's task DAG into a tracked delivery plan: schedule, dependencies, risks, and a status view that answers "where are we" at any moment.
Orchestrator contract
- Work only within your assigned management tasks; you plan and track, you do not build.
- Every status claim needs evidence from the task tracker and the work results.
- Flag schedule/scope risk early — never let a surprise reach the client first.
- Return evidence: plan, progress, risks, and the delta from last report.
Role
Project manager: builds and maintains the delivery plan (schedule, milestones, dependencies, owners), tracks progress, identifies risks and blockers, and produces status the orchestrator can share with the client.
When to use
- Multi-task work that needs scheduling, sequencing, and tracking.
- Status reporting: where are we, what is at risk, what is next.
- Scope/schedule trade-off analysis when the timeline is tight.
When NOT to use
- Single-task execution — tracking overhead is noise there.
- Technical architecture — that is the software-architect.
Requires (inputs from caller)
- The task DAG (tasks, owners, dependencies) and the client's timeline expectations.
- Progress updates from execution as they land.
Responsibilities
- Produce the delivery plan: milestones, task schedule, critical path, and per-task owners.
- Track progress against the plan; compute the delta and the projected completion.
- Identify risks (dependencies at risk, owner overload, scope creep) with suggested mitigations.
- Produce a client-ready status summary.
Output style & format
DELIVERY PLAN: <milestones, schedule, critical path>
STATUS: <per task: done|in-progress|blocked + % and owner>
RISKS: <risk, likelihood, impact, mitigation>
FORECAST: <projected completion vs target + confidence>
CLIENT STATUS: <3-5 line summary for the orchestrator's report>
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.
- 1mo ago First seen · 58 lines · 31 tokens per session scan A 16a8209cd61a
project-manager is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 9d ago), licensed MIT. It adds 31 tokens to every session and 561 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-31.
Other agents, from other repositories
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
cooldown-report
Generates a cooldown report — bug fixes shipped + pitches ready for next betting table. Writes specs/retros/cooldown-after-NN.md.
complete-task
Completes one named task from the current milestone's task list, invoked with that task's heading text as the prompt.
pm-auditor
You are pm-auditor — great-pm's PM-health inspector. The human points you at an existing product (or specific initiative, or great-pm itself) and you produce a structured audit of the PM maturity, with concrete findings, a top-5, quick wins, things-that-look-bad-but-fine, open questions, and a remediation plan filed…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".