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 skills/lteawoo/tokenmeter/tokenmeter-releasenpx skills add lteawoo/TokenMeter --skill tokenmeter-releasegit clone --depth 1 https://github.com/lteawoo/TokenMeterWhat 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.00094 | $0.02057 |
| Opus 5 | $0.00047 | $0.01028 |
| Sonnet 5 | $0.00019 | $0.00411 |
| Haiku 4.5 | $0.00009 | $0.00206 |
Grade A, and why
tokenmeter-release 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 3d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TokenMeter Release
TokenMeter의 macOS desktop release와 lteawoo/homebrew-tokenmeter cask 배포를 end-to-end로 처리한다.
원칙
master에 직접 커밋하지 않는다. 항상 목적이 분명한 작업 브랜치를 만든다.- 태그는 PR merge 후
origin/master와 동기화된 merge commit에만 찍는다. - cask
sha256은 반드시 실제 DMGshasum또는 GitHub Release asset digest와 일치시킨다. - source repo의
packaging/homebrew/Casks/tokenmeter.rb와 tap repo의Casks/tokenmeter.rb를 모두 같은 버전/SHA로 맞춘다. brew audit는 source repo 경로가 아니라 tap 기준으로 실행한다.- PR merge 메시지를 커스텀해서 issue auto-close가 누락되면 이슈를 수동으로
completed처리한다. - destructive git 명령은 쓰지 않는다.
사전 확인
먼저 현재 상태와 원격 상태를 확인한다.
git status --short --branch
git remote -v
git branch --show-current
git tag --sort=-version:refname
gh auth status
gh repo view --json nameWithOwner,defaultBranchRef,url
gh issue list --state open --limit 50
gh pr list --state open --limit 50
gh repo view lteawoo/homebrew-tokenmeter --json nameWithOwner,defaultBranchRef,url
현재 최신 GitHub Release와 cask 기준도 확인한다.
gh release view "v<current-version>" --repo lteawoo/TokenMeter --json tagName,isDraft,isPrerelease,publishedAt,assets,url
sed -n '1,80p' packaging/homebrew/Casks/tokenmeter.rb
변경 준비
- 작업 브랜치를 만든다.
git switch -c fix/<short-name>
- 필요하면 추적 이슈를 만든다.
gh issue create --repo lteawoo/TokenMeter --title "<title>" --body "<body>"
- 릴리즈 버전을 결정한다.
- 버그 수정: patch version
- 사용자 기능 추가: minor version
- 이미 배포된 tag/release는 수정하지 말고 새 버전으로 간다.
- 버전을 동기화한다.
package.jsonapps/dashboard/src-tauri/tauri.conf.jsonapps/dashboard/src-tauri/Cargo.tomlapps/dashboard/src-tauri/Cargo.lockREADME.mdpackaging/homebrew/Casks/tokenmeter.rb
cask SHA는 DMG 빌드 후 채운다. 임시 placeholder를 넣었다면 커밋 전 반드시 제거한다.
필수 검증
릴리즈 후보에서 다음을 실행한다.
pnpm --filter @tokenmeter/dashboard build
cargo test --manifest-path apps/dashboard/src-tauri/Cargo.toml
pnpm --filter @tokenmeter/dashboard tauri:build
DMG SHA와 번들 메타데이터를 확인한다.
shasum -a 256 apps/dashboard/src-tauri/target/release/bundle/dmg/TokenMeter_<version>_aarch64.dmg
defaults read "$PWD/apps/dashboard/src-tauri/target/release/bundle/macos/TokenMeter.app/Contents/Info" CFBundleShortVersionString
defaults read "$PWD/apps/dashboard/src-tauri/target/release/bundle/macos/TokenMeter.app/Contents/Info" LSUIElement
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.
- 3d ago First seen · 233 lines · 94 tokens per session scan A 98716d1e5eb4
tokenmeter-release is a skill published in the GitHub repository lteawoo/TokenMeter (6 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 2,057 once invoked, about $0.0005 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 skills, from other repositories
cut-release
Cuts a new versioned release of codex-trace end-to-end without asking any questions. Detects commits since the last ancestral tag, classifies them with conventional-commit rules to pick the semver bump, bumps every version-bearing file in sync, writes the CHANGELOG entry, commits and tags on a release branch, pushes…
release
Release pipeline for CLI, mobile, web, and server. Guides through version bumping, building, testing, publishing, and deploying. Replaces the old interactive release-it flow with a Claude Code-native experience. Use when user types /release or asks to release, publish, deploy, or ship any component.
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
map-release
Execute the mapify-cli package release workflow with validation gates and PyPI publication. Use when shipping a new MAP Framework release. Do NOT use for ordinary feature work; use map-efficient.