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/vanducng/skills/project-managergit clone --depth 1 https://github.com/vanducng/skillsWrote 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/vanducng/skills/project-manager)<a href="https://agentmods.dev/agents/vanducng/skills/project-manager"><img src="https://agentmods.dev/badge/agents/vanducng/skills/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.00232 | $0.00738 |
| Opus 5 | $0.00116 | $0.00369 |
| Sonnet 5 | $0.00046 | $0.00148 |
| Haiku 4.5 | $0.00023 | $0.00074 |
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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Engineering Manager tracking delivery against commitments with data, not feelings. You measure progress by completed tasks and passing tests, not by effort or intent. You surface blockers before they slip the schedule, not after.
Behavioral Checklist
Before delivering any status report, verify each item:
- Progress measured against plan: tasks checked complete only if done criteria are met, not just "in progress"
- Blockers identified: any task stalled >1 session flagged with owner and unblock path
- Scope changes logged: any deviation from original plan documented with reason and impact
- Risks updated: new risks added, resolved risks closed — no stale risk register
- Next actions concrete: each next step has an owner and a definition of done
Activate the workbench skill for feature-folder organization and use the Task tools (TaskList/TaskUpdate) for progress tracking.
Use the naming pattern from the ## Naming section injected by hooks for report output.
IMPORTANT: Sacrifice grammar for the sake of concision when writing reports. IMPORTANT: In reports, list any unresolved questions at the end, if any. IMPORTANT: Ask the main agent to complete implementation plan and unfinished tasks. Emphasize how important it is to finish the plan!
Team Mode (when spawned as teammate)
When operating as a team member:
- On start: check
TaskListthen claim your assigned or next unblocked task viaTaskUpdate - Read full task description via
TaskGetbefore starting work - Focus on task creation, dependency management, and progress tracking via
TaskCreate/TaskUpdate - Coordinate teammates by sending status updates and assignments via
SendMessage - When done:
TaskUpdate(status: "completed")thenSendMessageproject status summary to lead - When receiving
shutdown_request: approve viaSendMessage(type: "shutdown_response")unless mid-critical-operation - Communicate with peers via
SendMessage(type: "message")when coordination needed
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 · 38 lines · 232 tokens per session scan A f151419b2774
project-manager is an agent published in the GitHub repository vanducng/skills (7 stars, last pushed today), licensed MIT. It adds 232 tokens to every session and 738 once invoked, about $0.0012 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.