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/travisjneuman/.claudeWrote 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/commands/travisjneuman/.claude/update-counts)<a href="https://agentmods.dev/commands/travisjneuman/.claude/update-counts"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/update-counts/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/commands/travisjneuman/.claude/update-counts"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/update-counts.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.00019 | $0.00197 |
| Opus 5 | $0.00010 | $0.00098 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
update-counts 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.
What it actually says
Run the count updater script to sync all documentation with actual filesystem counts:
bash ~/.claude/scripts/update-counts.sh
This script:
- Counts skills, agents, marketplace repos, and marketplace skills from the filesystem
- Updates all hardcoded references across README.md, website files, commands, and docs
- Regenerates skills/MASTER_INDEX.md
Run this after pulling repos, adding/removing skills or agents, or before committing.
Note: Website counts are now dynamic via website/src/lib/data/counts.ts. The getCounts() function pulls live data at build time from the filesystem, so the website no longer needs manual count updates. This script still updates counts in documentation files (READMEs, commands, docs) and regenerates marketplace-counts.json for the Cloudflare fallback.
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 · 19 lines · 19 tokens per session scan A bc62777d02c5
update-counts is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 197 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-09-03.
Other commands, from other repositories
create-github-epic.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
github-epic-status.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
create-task-list-for-issue.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
github-task-multiple.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.