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 commands/baodq97/open-plugin/coachgit clone --depth 1 https://github.com/baodq97/open-pluginWhat 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.00015 | $0.00400 |
| Opus 5 | $0.00008 | $0.00200 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
coach 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 2d 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
Provide coaching on SFIA skills for the active role.
Instructions
-
Determine the role:
- Read
.profile-playbook/sessions/to find the most recent session - Read
{workspace}/state.yamlto get therolefield - If no active session and a role name is provided as argument (sa, po, ba, testing, pm, ea, cio, cto, cpo), use that role
- If no session and no role, ask the user which role they want coaching for
- Read
-
Load role-specific coaching resources:
- Skill descriptions:
skills/{role}-playbook/references/sfia-skill-map.md - Coaching prompts:
skills/{role}-playbook/references/coaching-prompts.md
- Skill descriptions:
-
If a SFIA skill code is provided (e.g.,
ARCH,TEST,PRMG):- Show the skill name, category, and overall description
- Show level descriptions for the role's relevant levels (typically 4, 5, 6 — or 5, 6, 7 for senior roles)
- Explain the key transitions between levels
- Provide practical exercises to build competency at each level
- Give examples of good vs. insufficient output at each level
-
If no skill code provided:
- Show an overview table of all SFIA skills relevant to the role with:
- Skill name and code
- Level range
- One-line description of what it means for this role
- Ask the user which skill they want to deep-dive into
- Show an overview table of all SFIA skills relevant to the role with:
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.
- 2d ago First seen · 34 lines · 15 tokens per session scan A d13b63d236d6
coach is a command published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 400 once invoked, about $0.0001 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 commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
performance-audit-static
Static performance audit of AI-built code — find N+1 queries and request waterfalls, over-fetching, missing indexes, and caching opportunities, ranked by effort and impact.
sprint
Sprint lifecycle — plan a sprint, run a retrospective, or generate release notes.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
analyze-test
Analyze A/B test results — statistical significance, sample size validation, and ship/extend/stop recommendations.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.