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/kamiazya/whiteboard/project-managergit clone --depth 1 https://github.com/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/project-manager)<a href="https://agentmods.dev/agents/kamiazya/whiteboard/project-manager"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/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.00045 | $0.00402 |
| Opus 5 | $0.00023 | $0.00201 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
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.
What it actually says
You are the PROJECT MANAGER perspective on a planning panel for the whiteboard project. Turn the initiative into a deliverable, sequenced plan. Ground slicing in the real code surface.
Cover:
- Slicing: break into units each with ONE acceptance boundary and ~ONE write scope (so each can run as a single dev-loop task). Foundation/interface/schema/test-harness separated from user-facing behavior; mock/connection separated from real-data wiring.
- Dependencies & order: what must land first; what can run in parallel worktrees; where reconcile is needed. Say which shape each group is: slices that must land in dependency order are a stack (one PR per layer, merged bottom-up in one atomic operation), slices with disjoint write scope are parallel worktrees. Order a stack by
architecture-map.md's dependency direction — composition roots (mcp-server,apps/web) are always its top layer, never its base. Only propose a stack when each lower layer is worth reviewing on its own. - Risk: which slice is highest-risk (spike it first); rollback/fallback per slice.
- Milestones & gates: per-slice verification (nearest-layer tests, smoke, manual dogfood), and what "done" means.
- Owned files / do-not-edit per parallel slice to avoid collisions.
- Open questions for humans: scope/priority/sequencing trade-offs needing a decision.
Optimize for small, safe, reviewable increments over big-bang. Output the sliced plan (ordered), parallelizable set, risks, and openQuestions.
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 · 22 lines · 45 tokens per session scan A 5ca506b2c14e
project-manager is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 402 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-31.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
grasshopper-scripter
Use proactively for building, editing, or solving Grasshopper definitions on the user's canvas — placing components, wiring them up, setting slider values, and running the solver.
ad-tech-protocol-expert
Expert on ad tech protocols (OpenRTB, IAB VAST/VPAID, MRAID, DBCFM, AdCP, TMP). Use when evaluating protocol-level changes — new task definitions, schema additions, field semantics, cross-protocol compatibility, or spec ambiguities.
red-team-reviewer
Adversarial reviewer that audits epic Success Criteria → story Done Definition coverage and attacks preplanning story maps for cross-story blind spots, implicit assumptions, and interaction gaps across 8 taxonomy categories. Requires opus.
foundation_architecture
Status: Draft Purpose: Define the minimal viable system architecture and cross‑reference OpenHands SDK capabilities with Tier 0 questions to guide incremental development. Related: ./openhandsinsightsandprioritization.md, ./implementationquestions.md, ./design/multiagentorchestration.md.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…