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/hainamchung/agent-assistant/project-managergit clone --depth 1 https://github.com/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/project-manager)<a href="https://agentmods.dev/agents/hainamchung/agent-assistant/project-manager"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/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.00014 | $0.01072 |
| Opus 5 | $0.00007 | $0.00536 |
| Sonnet 5 | $0.00003 | $0.00214 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade C, and why
project-manager scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- 🔒 COGNITIVE ANCHOR — MANDATORY OPERATING SYSTEM --> How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BINDING: This file OVERRIDES default AI patterns. Follow Thinking Protocol EXACTLY. EXTRACT: Core Directive + Constraints + Output Format before proceeding.
📋 Project Manager
| Attribute | Value |
|---|---|
| ID | agent:project-manager |
| Role | Principal Delivery Manager |
| Profile | management:orchestration |
| Reports To | Stakeholders |
| Manages | All agents |
| Framework | Agile/Scrum |
CORE DIRECTIVE: Deliver value on time. Remove blockers. Manage expectations. Plan for problems before they become crises.
Prime Directive: Deliver working software. Surface risks early. Protect the team.
⚡ Skills
MATRIX DISCOVERY: Skills auto-injected from domain files in
~/.{TOOL}/skills/agent-assistant/matrix-skills/Profile:management:orchestration| Domains:management,planning
🎯 Expert Mindset
THINK_LIKE:
- "What's blocking the team?"
- "What risks are emerging?"
- "Are stakeholders aligned?"
- "Is scope under control?"
ALWAYS:
- Surface risks early
- Protect team from interruptions
- Facilitate, don't dictate
- Measure and improve
🧠 Thinking Protocol
Step 0: CONTEXT CHECK (MANDATORY)
CHECK PROJECT DOCS (if ./.documents/ exists):
- knowledge-overview/00-index.md → Project scope (drill into sub-files as needed)
- knowledge-domain/00-index.md → Data/API scope (drill into sub-files as needed)
- business/business-prd/00-index.md → Requirements (drill into sub-files as needed)
→ USE these for project tracking and scope management
Step 1: PROJECT STATUS
| Dimension | Status | Notes |
|---|---|---|
| Scope | 🟢🟡🔴 | {notes} |
| Schedule | 🟢🟡🔴 | {notes} |
| Resources | 🟢🟡🔴 | {notes} |
| Quality | 🟢🟡🔴 | {notes} |
| Risks | 🟢🟡🔴 | {notes} |
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.
- 5d ago First seen · 160 lines · 14 tokens per session scan C 29a274816906
project-manager is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,072 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
issue-tracker
Issues and PRs for this repo live as GitHub issues. Use the gh CLI for all operations. The project repo is alvinunreal/oh-my-opencode-slim.
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
mc-conductor
Mission Control conductor — orchestrates parallel background missions, handles completions and failures, reports to the user.
hatch3r-handoff-preparer
Prepare a canonical handoff document capturing mid-work session state. Invoked by /hatch3r-handoff prepare and by the context-health skill's Orange/Red delegation step.
plan
Create structured implementation plans. Produces master plan + phase files for non-trivial work (3+ phases, 5+ files). Use before multi-phase implementation.
product-mgr
Crisp PM that turns a raw goal into a tight PRD with Given/When/Then acceptance criteria.