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 instructions/lranslot/tokenomamoritool/claude-mdgit clone --depth 1 https://github.com/lranslot/TokenOmamoriToolWrote 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/instructions/lranslot/tokenomamoritool/claude-md)<a href="https://agentmods.dev/instructions/lranslot/tokenomamoritool/claude-md"><img src="https://agentmods.dev/badge/instructions/lranslot/tokenomamoritool/claude-md.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.02612 | $0.02612 |
| Opus 5 | $0.01306 | $0.01306 |
| Sonnet 5 | $0.00522 | $0.00522 |
| Haiku 4.5 | $0.00261 | $0.00261 |
Grade A, and why
TokenOmamoriTool CLAUDE.md 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 5d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project status
Core features (monitoring, RTK/ccusage/claude-mem integration, install/uninstall UI, tray
residency, ja/en localization, donation flow, omamori visual theme) are implemented. All
requirements live in docs/:
docs/仕様書_統合版_v1.0.md— the spec (§1–§13, all implemented): features/UI/scope (§1–§5), resolved research answers — log paths, tool output formats, install methods (§6), tray residency (§8), donation prompts (§9–§10), §11 Japanese/English localization (including the §11.7 bilingual README.md), §12 omamori visual theme (palette, tray/app icons, washi main-window styling), §13 portable EXE distribution (publish script, versioning, GitHub Releases, README distribution notes). Consolidates the former 6 spec files; § numbers are unchanged.
This file in docs/ is the authoritative spec. If code, comments, or this CLAUDE.md ever
disagree with it, the spec wins. (docs/実装メモ_アーキテクチャ詳細.md holds implementation
details and gotchas, referenced from the architecture notes below.)
App display name: 「トークン節約お守りツール」.
What this tool is
A Windows WPF tray/overlay app ("Claude Code トークン節約お守りツール") that monitors a Claude Code dev environment and helps install/measure token-saving tools: RTK, ccusage, claude-mem. Policy constraints from the spec (do not violate these when implementing features):
- Never reduce the AI's own output/response quality to save tokens — only optimize I/O and memory layers.
- The tool itself must not consume tokens (no API calls for measurement).
- Explicitly out of scope: Caveman, kizami, Token Optimizer/Savior, Context Mode (see spec §4.3 "導入しないもの" for reasons).
Build & run
dotnet build TokenOmamoriTool.sln -v q -nologo
dotnet run --project TokenOmamoriTool/TokenOmamoriTool.csproj
dotnet test -v q -nologo
Token-saving rule for development: always pass -v q -nologo to dotnet build / dotnet test.
When reporting build/test runs, output one line on success (OK / pass count) and full details only
on failure.
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.
- 5d ago First seen · 131 lines · 2,612 tokens per session scan A 3472048ae5e9
TokenOmamoriTool CLAUDE.md is an instructions file published in the GitHub repository lranslot/TokenOmamoriTool (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,612 tokens to every session, about $0.0131 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).