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 skills add coltonjosephdean-rgb/talk-to-anyone --skill coach-endgit clone --depth 1 https://github.com/coltonjosephdean-rgb/talk-to-anyoneWrote 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/skills/coltonjosephdean-rgb/talk-to-anyone/coach-end)<a href="https://agentmods.dev/skills/coltonjosephdean-rgb/talk-to-anyone/coach-end"><img src="https://agentmods.dev/badge/skills/coltonjosephdean-rgb/talk-to-anyone/coach-end/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/skills/coltonjosephdean-rgb/talk-to-anyone/coach-end"><img src="https://agentmods.dev/badge/skills/coltonjosephdean-rgb/talk-to-anyone/coach-end.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.00026 | $0.00192 |
| Opus 5 | $0.00013 | $0.00096 |
| Sonnet 5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
coach-end 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 13d 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-end — back to normal
The user wants to stop talking to the active coach persona.
- If a coach persona is active in this conversation, drop it completely — no more first-person speech as that person, no more of their voice or catchphrases.
- Confirm in one short line as Claude, e.g.:
Coach session with {Name} ended — you're back with Claude. The persona stays saved;
/coach {name}brings them back any time. - If no persona is active, just say there's no coach session running and that
/coach <name>starts one.
Do not delete anything from the persona cache — ending a session never destroys the persona file.
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.
- 13d ago First seen · 21 lines · 26 tokens per session scan A f41b994a8216
coach-end is a skill published in the GitHub repository coltonjosephdean-rgb/talk-to-anyone (60 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 192 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-30.
Other skills, from other repositories
self-improve
The deliberate self-improvement loop for the maintainer — step back from fixing issues and improve Heimdall's OWN capability. Ports karpathy/autoresearch to Heimdall's routing/planning: collect evidence from metrics.jsonl + queue dead/done stats → form testable hypotheses → run a bounded routing experiment → evaluate…
stacks
Load stack-specific knowledge (conventions, exact lint/test/build commands, common failure patterns) onto the current role agent for the project's detected tech stack(s) — Next.js, React Native, Spring Boot, FastAPI, Django, Rust, etc. Use at the start of any task in an unfamiliar or newly-onboarded repo, or whenever…
transmute
Comprehend an existing feature, then PORT it to another app (optionally upgrading it) or INTEGRATE/transform it in place — including swapping the vendor behind the scenes while preserving the exact UX. Use for "port/re-implement/clone this feature into ", "swap/migrate the vendor behind but keep the UX", "figure out…
confluence
Work with Confluence over its REST API (no MCP) — read/search (CQL), summarize pages, find docs, create/update/comment/label. Use for any read/search/create/update on Confluence pages, or references to a remembered space, page, or doc.
divine
Thorough, research-grounded code review of a change, PR, or MR — multi-lens (correctness, security, simplification, tests), severity-ranked with impact + fix, configurable depth, optional PR comments. Use when asked to review code, "do a code review", "review this PR/MR", "review my changes/diff/branch", or audit a…
conjure
Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code.