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/josheche/tokengolfWrote 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/plugins/josheche/tokengolf/plugin)<a href="https://agentmods.dev/plugins/josheche/tokengolf/plugin"><img src="https://agentmods.dev/badge/plugins/josheche/tokengolf/plugin/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/plugins/josheche/tokengolf/plugin"><img src="https://agentmods.dev/badge/plugins/josheche/tokengolf/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tokengolf 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
{
"name": "tokengolf",
"version": "1.1.2",
"description": "Gamify your Claude Code sessions — track token efficiency, earn achievements, level up your prompting.",
"homepage": "https://josheche.github.io/tokengolf/"
}
What it installs
The manifest is a name and a version. 3 commands, 8 hooks travel with it, and installing the plugin installs all of them — 49 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command config A 15 tokens
- Command scorecard A 18 tokens
- Command stats A 16 tokens
- Hook PostToolUseFailure A not measured
- Hook Stop A not measured
- Hook PreCompact A not measured
- Hook PostToolUse A not measured
- Hook UserPromptSubmit A not measured
- Hook SessionEnd A not measured
- Hook SubagentStart A not measured
- Hook SessionStart A not measured
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 · 7 lines scan A 5197fab6ad1f
tokengolf is a plugin published in the GitHub repository josheche/tokengolf (2 stars, last pushed 7mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
slime
Your work goals are the bosses. Your plugins are your gear. Watch Claude fight — a zero-impact RPG layer over Claude Code.
claude-pet
A desktop pet that grows as you code with Claude Code — read-only state engine, Electron widget, reminders, and achievements.
cc-xp
A Claude Code status line that turns Claude-only token usage into an experience-points display with levels, titles, and a progress bar. It also includes separate role-playing-game-style rewards and a cosmetics shop.
claude-code-achievements
Steam-style achievement system for Claude Code.
codotchi
ClaudeCodotchi - idle time tracker for Claude Code that grows when you respond quickly!
agent-deck
Complete guide for managing AI coding agent sessions via agent-deck CLI - session lifecycle, MCP management, groups, profiles, and automation.