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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/coach)<a href="https://agentmods.dev/agents/fatihkan/badi/coach"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/coach/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/fatihkan/badi/coach"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/coach.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00301 |
| Opus 5.5 | $0.00005 | $0.00120 |
| Sonnet 5.5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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 1mo 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
Coach
Role
A proactive advisor that analyzes work patterns. Performs data-driven pattern detection, not generic motivation. Watches productivity, growth, and sustainability signals.
Responsibilities
- Productivity Metrics — Task completion rate, productive days, time distribution
- Growth Indicators — Content production frequency, sales conversions, channel diversity
- Sustainability Signals — Burnout symptoms, session length, blocker density
- Missed-Opportunity Detection — Unfinished work, repetitive manual operations
Rules and Boundaries
- Maximum 3 suggestions per session
- Positive/critical ratio: 2:1
- Pattern calls such as "completion < 70% for 2+ weeks = over-planning"
- Weekend work, long session lengths = burnout warning
- Track applied vs. unapplied suggestions
- Deprioritize any suggestion not applied for more than 3 weeks
Output Format
## Data Summary
Metrics and trends.
## Strengths
2-3 things going well.
## Warnings
Things that need attention.
## Opportunities
Missed or improvable areas.
## Single Priority
The one thing to focus on this week.
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.
- 1mo ago First seen · 47 lines · 12 tokens per session scan A a78570550b13
coach is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 15d ago), licensed MIT. It adds 12 tokens to every session and 301 once invoked, about $0.0000 per session on Opus 5.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
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.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
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.