Agent Builder
shareAI-lab/learn-claude-code
Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.
A skill your agent uses when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification.
Install Token Meter Verification
$ npx skills add splunk/token-meter --skill token-meter-verification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install splunk/token-meter token-meter-verification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/splunk/token-meter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/token-meter-verification .claude/skills/token-meter-verification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "token-meter-verification" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verification into .claude/skills/token-meter-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-verification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add splunk/token-meter --skill token-meter-verification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install splunk/token-meter token-meter-verification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/token-meter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/token-meter-verification .agents/skills/token-meter-verification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "token-meter-verification" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verification into .agents/skills/token-meter-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-verification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add splunk/token-meter --skill token-meter-verification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install splunk/token-meter token-meter-verification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/token-meter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/token-meter-verification .cursor/skills/token-meter-verification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "token-meter-verification" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verification into .cursor/skills/token-meter-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-verification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/splunk/token-meter.git --path .agents/skills/token-meter-verification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add splunk/token-meter --skill token-meter-verification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install splunk/token-meter token-meter-verification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/token-meter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/token-meter-verification .gemini/skills/token-meter-verification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "token-meter-verification" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verification into .gemini/skills/token-meter-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-verification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install splunk/token-meter token-meter-verificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add splunk/token-meter --skill token-meter-verification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/splunk/token-meter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/token-meter-verification .github/skills/token-meter-verification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "token-meter-verification" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verification into .github/skills/token-meter-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-verification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add splunk/token-meter --skill token-meter-verification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install splunk/token-meter token-meter-verification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/token-meter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/token-meter-verification .opencode/skills/token-meter-verification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "token-meter-verification" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-verification into .opencode/skills/token-meter-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-verification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
token-meter-verification- GitHub stars
- 114
- Token cost
- ~620 tokens
- SKILL.md length
- 291 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification.
- Token Meter changes
- SKILL.md covers Purpose, Build the verification matrix, Evidence rules and Tester result
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Claims need independent source
What it does
Token Meter Verification is an agent skill from splunk/token-meter. Use when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification.
Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering. The repository describes itself as: Open-source, local-first AI coding agent usage and cost dashboard for Claude Code, Codex, Cursor, OpenCode, Kiro, and Pi. The licence is MIT.
When your agent uses it
- Token Meter changes
- Claims need independent source
- Platform verification
Example prompts
- “/token-meter-verification”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit f34c78b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Token Meter Verification loads about 620 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 291 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from splunk/token-meter at commit f34c78b, republished under its MIT licence (© splunk). 291 words, ~620 tokens.
Download SKILL.mdSave it as
.claude/skills/token-meter-verification/SKILL.md (or your agent's skills folder).- name
- token-meter-verification
- description
- Use when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification.
Token Meter Verification
Purpose
Independently verify the task envelope's acceptance criteria against one exact head. Do not modify tracked files or repair failures while acting as tester.
Build the verification matrix
Read specs/AGENTS.md, the task envelope, developer result, current diff, and
.agents/workflow/review-policy.yaml. Select checks from the surfaces the diff can
affect:
| Surface | Evidence |
|---|---|
| Python and contracts | Focused tests, full suite when proportionate, and py_compile |
| Dashboard | Embedded-JavaScript parse plus live wide-desktop and 1024-pixel-laptop interaction checks |
| Dashboard styling | tests.contracts.test_design_system, a scripts/style-snapshot.js base-versus-head diff at 1440 and 1024 px (changes limited to the claimed deltas, no new overflow or clipping), and rendered HTML and SVG text of 11px or more |
| Native menu | Swift compile, deterministic smoke output, and live menu behavior |
| Packaging | Installer syntax, manifest coverage, installed-runtime revision, and source/runtime parity |
| HTTP behavior | /health, relevant endpoint payloads, cache/privacy boundaries, and failure states |
| Cross-platform | Target-host parse, launch, interaction, update, and uninstall evidence |
Run focused checks first, then the broader checks required by risk. Synthetic fixture passes do not replace real upstream, installed-runtime, or visible behavior where the acceptance criteria depend on them.
Evidence rules
- Record the command or interaction, outcome, and inspected head.
- Use
passed,failed,blocked, ornot-run; never turn missing evidence into a pass or measured zero. - Separate source checks from live installed behavior.
- Confirm source/runtime parity after installation rather than assuming the checkout is what the user sees.
- Preserve exact target-host limitations. macOS evidence does not prove Windows or Linux behavior.
- Stop and report a failure; return the change to the developer instead of fixing it.
Tester result
Return acceptance-criteria coverage, commands and live checks, counts where useful, the exact head, failures, not-run checks, unverified behavior, blockers, and the recommended next state. A later tracked code or test change invalidates the result.
© splunk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/token-meter-verification of splunk/token-meter.
Open the folder on GitHubat commit f34c78b
Compare with similar skills
Token Meter Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Token Meter Verification this skillsplunk/token-meter | 114 | — | ~620 | Automated safety check: Pass | MIT | |
| Agent BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Add Uint Supportpytorch/pytorch | 104k | 2 repos | ~2.3k | Automated safety check: Pass | Custom licence | |
| LLM Benchmarking with lm-evaluation-harnessOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3k | Automated safety check: Pass | MIT | |
| Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3.3k | Automated safety check: Pass | MIT | |
| 1passwordtrpc-group/trpc-agent-go | 1.9k | 14 repos | ~656 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Add Uint Support
pytorch/pytorch
Add unsigned integer (uint) type support to PyTorch operators by updating ATDISPATCH macros.
LLM Benchmarking with lm-evaluation-harness
Orchestra-Research/AI-Research-SKILLs
Runs lm-evaluation-harness to benchmark language models on academic suites such as MMLU, GSM8K and HumanEval, compare models and track training checkpoints.
Segment Anything Model Guide
Orchestra-Research/AI-Research-SKILLs
Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.
1password
trpc-group/trpc-agent-go
Set up and use 1Password CLI (op). An agent skill from trpc-group/trpc-agent-go.
Planning With Files
jarrodwatts/claude-code-config
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage.
More from splunk/token-meter
Token Meter Communication
splunk/token-meter
A skill your agent uses when a Token Meter task will produce Slack, GitHub, release, contributor, or user-facing status communication.
Token Meter Development
splunk/token-meter
A skill your agent uses when a Token Meter issue or approved feature needs diagnosis or implementation in the repository.
Token Meter GitHub Ops
splunk/token-meter
A skill your agent uses when Token Meter GitHub issues, pull requests, review requests, checks, comments, merges, or closure need to be managed.
Token Meter Review
splunk/token-meter
A skill your agent uses when a Token Meter change needs independent requirements, correctness, regression, privacy, or cross-surface review.
Token Meter Intake
splunk/token-meter
A skill your agent uses when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.
Related
Categories
Questions about Token Meter Verification
What does Token Meter Verification do?
A skill your agent uses when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification. Token Meter Verification is an agent skill from splunk/token-meter. Use when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification.
When should I use Token Meter Verification?
Token Meter Verification fits situations like: token Meter changes; claims need independent source; platform verification.
How do I install Token Meter Verification in Claude Code?
Run `npx skills add splunk/token-meter --skill token-meter-verification -a claude-code`. Or copy the skill folder (.agents/skills/token-meter-verification in splunk/token-meter) into .claude/skills/token-meter-verification in your project. Claude Code loads it when a task matches its description.
How do I install Token Meter Verification in Codex?
Run `npx skills add splunk/token-meter --skill token-meter-verification -a codex`. Or copy the skill folder (.agents/skills/token-meter-verification in splunk/token-meter) into .agents/skills/token-meter-verification in your project. Codex loads it when a task matches its description.
Can I use Token Meter Verification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add splunk/token-meter --skill token-meter-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/token-meter-verification, .gemini/skills/token-meter-verification, .github/skills/token-meter-verification and .opencode/skills/token-meter-verification in your project.
What does Token Meter Verification need to run?
SKILL.md names no scripts, command-line tools or credentials: Token Meter Verification is instructions for the agent only. Our summary lists: Python 3.
Does Token Meter Verification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Token Meter Verification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Token Meter Verification use?
Token Meter Verification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Token Meter Verification use?
About 620 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Token Meter Verification?
Skills that share tags, products or a category with Token Meter Verification: Agent Builder (shareAI-lab/learn-claude-code, 78k stars), Add Uint Support (pytorch/pytorch, 104k stars), LLM Benchmarking with lm-evaluation-harness (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Segment Anything Model Guide (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Token Meter Verification?
splunk (a GitHub organization) maintains it in splunk/token-meter, which has 114 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: splunk/token-meter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.