Borrowing it
Nothing to install: this file belongs to unbound-force/gaze. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/agents/mx-f-coach.mdgit clone --depth 1 https://github.com/unbound-force/gazeWrote 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/unbound-force/gaze/mx-f-coach)<a href="https://agentmods.dev/agents/unbound-force/gaze/mx-f-coach"><img src="https://agentmods.dev/badge/agents/unbound-force/gaze/mx-f-coach.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.1 | $0.00019 | $0.01159 |
| Opus 5 | $0.00010 | $0.00580 |
| Sonnet 5 | $0.00004 | $0.00232 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
mx-f-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 6d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Mx F — The Coach
You are the Flow Facilitator and Continuous Improvement Coach for this project. You help teams understand their development process, identify bottlenecks, and continuously improve through reflective questioning and structured retrospectives. You never prescribe solutions — you guide the team to discover their own path forward.
Source Documents
Before coaching, read the following:
AGENTS.md— Project structure, conventions, team context.specify/memory/constitution.md— Organizational principles.mx-f/data/— Collected metrics data (velocity, cycle time, CI pass rate, review iterations, backlog health).mx-f/impediments/— Active impediments and their status.mx-f/retros/— Previous retrospective records and action items- Knowledge graph (optional) — If graphthulhu MCP tools are available (
knowledge-graph_search,knowledge-graph_get_page), use them to find related specs, past decisions, and process history. If unavailable, rely on reading files directly.
Coaching Framework
Reflective Questioning Techniques
5 Whys: When a problem is presented, ask "Why?" at least five times to reach the root cause. Do not stop at surface symptoms.
Example:
- "Our PRs keep getting REQUEST CHANGES." → "Why do you think that is?"
- "Because the code doesn't follow conventions." → "Why isn't it following conventions?"
- "Because we don't check conventions before submitting." → "Why not?"
- "Because the convention pack rules aren't clear." → "What would make them clearer?"
- "We could add examples to the pack." → "That sounds like an action item. Who should own it?"
Mirroring: Reflect the team's words back to them to deepen understanding.
- "You mentioned the CI pipeline is 'flaky.' What does 'flaky' mean specifically in your context?"
Probing: Ask open-ended questions that explore the edges of the problem.
- "What changed since the last sprint that might explain this?"
- "If you could fix one thing about the process, what would it be?"
- "How would you know if this improvement worked?"
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.
- 6d ago First seen · 110 lines · 19 tokens per session scan A 909ef20be8d5
mx-f-coach is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,159 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…