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 agentmods add commands/krishnesh7/claude-usage-analytics/project-confirmgit clone --depth 1 https://github.com/krishnesh7/claude-usage-analyticsWrote 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/krishnesh7/claude-usage-analytics/project-confirm)<a href="https://agentmods.dev/commands/krishnesh7/claude-usage-analytics/project-confirm"><img src="https://agentmods.dev/badge/commands/krishnesh7/claude-usage-analytics/project-confirm.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 | $0.00031 | $0.00316 |
| Opus 5 | $0.00015 | $0.00158 |
| Sonnet 5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
project-confirm 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 4d 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
Show the current session's project assignment and confidence, then offer to correct it if needed.
Run the following and present the results clearly:
CU=${CLAUDE_PLUGIN_ROOT}/bin/cu
# Resolve the current directory
echo "=== Project resolution for: $(pwd) ===" && \
$CU session-resolve --cwd "$(pwd)"
After showing the output, explain:
- EXACT/SUBDIR/WORKTREE — correctly auto-tagged, no action needed
- FUZZY — loosely matched; ask: "Is this correct? If not, which registered project should it be?" Then run:
$CU project tag --session $CLAUDE_SESSION_ID --name <correct-name> - AMBIGUOUS — multiple matches; ask: "Which of these projects does this session belong to?" Then run:
$CU project tag --session $CLAUDE_SESSION_ID --name <chosen-name> - UNMATCHED — ask: "What project is this session for?" Options:
- Tag an existing project:
$CU project tag --session $CLAUDE_SESSION_ID --name <name> - Register & tag a new one: run
cu project init <name>in the terminal, then tag
- Tag an existing project:
Also show registered projects with: $CU project list
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.
- 4d ago First seen · 27 lines · 31 tokens per session scan A 6dfcde99505f
project-confirm is a command published in the GitHub repository krishnesh7/claude-usage-analytics (2 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 316 once invoked, about $0.0002 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 commands, from other repositories
graph-report
Governance metrics dashboard — coverage by category, cross-reference density, compliance readiness, and project comparison across all working projects.
octo-plan
Intelligent plan builder - creates strategic execution plans (doesn't execute). Use /octo:embrace to execute plans.
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
sync-github
Ejecuta SonIA Sync: refleja el tablero local en GitHub Issues usando gh CLI.