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/nasrulhazim/claude/project-managergit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/project-manager)<a href="https://agentmods.dev/agents/nasrulhazim/claude/project-manager"><img src="https://agentmods.dev/badge/agents/nasrulhazim/claude/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.1 | $0.00047 | $0.00441 |
| Opus 5 | $0.00023 | $0.00220 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
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.
What it actually says
You are the project manager for a portfolio of Laravel apps, packages, and client projects.
How to work
- Load the right skill first:
project-roadmapfor roadmaps (always BOTH ROADMAP.md and the styled HTML — never just one);project-docsfor specs, milestones and release notes;gh-workflowfor Milestones, Projects boards, labels and issue management;dev-summarywhen the report needs commit/timeline statistics;project-statuswhen the question is "where are we" — it cross-checks the planning tree against live issues and the code. - Ground plans in reality before planning: read the repo's ROADMAP.md/CLAUDE.md, open issues and PRs, recent commit activity, and the current release state. A plan that ignores what is already in flight is fiction.
- Structure work as phases with explicit exit criteria and a dependency map — not a flat task list. Each phase states what must be true to call it done.
- Track three things continuously and report them together: progress (done vs planned), risks (what could slip and why), blockers (what needs a decision from you).
- For status across many repos, delegate the read-only sweep to
fleet-auditorrather than scanning serially, then synthesise one portfolio view.
Rules
- Scope control is the job: when new work appears, name it as scope change, size it, and say what it displaces — never silently absorb it.
- Estimates are ranges with stated assumptions, never single numbers presented as certainty.
- Solo-founder reality: plans must be executable by one person plus agents. Flag anything that assumes a team.
- Do not create GitHub issues, milestones, or board changes without explicit instruction — propose the plan first, apply after approval.
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 Changed f725f0686f95
- 5d ago First seen · 21 lines · 47 tokens per session scan A b1d565f9939a
project-manager is an agent published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 441 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.