Async Communication Etiquette
aiming-lab/MetaClaw
A skill your agent uses when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately.
A skill your agent uses when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.
Install Token Meter Intake
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add splunk/token-meter --skill token-meter-intake -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install splunk/token-meter token-meter-intake --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-intake .claude/skills/token-meter-intake && 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-intake" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-intake into .claude/skills/token-meter-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-intake", 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-intakeType 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-intake -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install splunk/token-meter token-meter-intake --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-intake .agents/skills/token-meter-intake && 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-intake" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-intake into .agents/skills/token-meter-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-intake", 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-intake -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install splunk/token-meter token-meter-intake --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-intake .cursor/skills/token-meter-intake && 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-intake" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-intake into .cursor/skills/token-meter-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-intake", 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-intake--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-intake -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install splunk/token-meter token-meter-intake --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-intake .gemini/skills/token-meter-intake && 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-intake" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-intake into .gemini/skills/token-meter-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-intake", 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-intakeInstalls 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-intake -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-intake .github/skills/token-meter-intake && 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-intake" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-intake into .github/skills/token-meter-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-intake", 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-intake -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-intake --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-intake .opencode/skills/token-meter-intake && 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-intake" agent skill from https://github.com/splunk/token-meter/tree/main/.agents/skills/token-meter-intake into .opencode/skills/token-meter-intake/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "token-meter-intake", 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-intake- GitHub stars
- 110
- Token cost
- ~1.4k tokens
- SKILL.md length
- 765 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.
- A Token Meter Slack
- SKILL.md covers Purpose, Context first, Human response and Reporter end-to-end delivery, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- GitHub request needs contextual intake
What it does
Token Meter Intake is an agent skill from splunk/token-meter. Use when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.
Its SKILL.md is about 1.4k 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. It works with GitHub and Slack. 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
- A Token Meter Slack
- GitHub request needs contextual intake
Example prompts
- “/token-meter-intake”
What it can do on your machine
Read from SKILL.md and the folder at commit 4ff456b. 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 Intake loads about 1.4k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 765 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningTells the agent its actions are pre-authorized / not to stop for confirmationSKILL.md:43
existing thread. Do not pause for another approval between those steps. Recheck and
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 4ff456b, republished under its MIT licence (© splunk). 765 words, ~1,388 tokens.
Download SKILL.mdSave it as
.claude/skills/token-meter-intake/SKILL.md (or your agent's skills folder).- name
- token-meter-intake
- description
- Use when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.
Token Meter Intake
Purpose
Turn feedback into a truthful human response and an actionable work envelope. Intake does not grant implementation or external-write authority.
Context first
- Open a Slack permalink through the Slack integration so attachments and the complete thread are included; do not reconstruct channel and timestamp values by hand.
- Read the linked GitHub issue or pull request in full, including comments and cited evidence. If a link is unavailable or ambiguous, ask for the correct source rather than implementing the paraphrase.
- Separate observed behavior, reporter interpretation, and open product decisions.
- Inspect current repository and dirty-tree ownership before promising a change.
Human response
Draft a short acknowledgment in the thread's tone. Say what is understood, what is being checked, and what input is still needed. Do not invent a diagnosis, deadline, or completion claim.
Except for the reporter-end-to-end route and the two narrow standing exceptions
below, every Slack message or GitHub comment is a separate external action. Preview
the exact text and obtain explicit approval for that message immediately before
posting. An approval for investigation, code, or a previous message does not cover a
later reply.
Reporter end-to-end delivery
When Pratik explicitly asks to start the Token Meter team flow or manage a linked
reporter request end to end, select the reporter-end-to-end route. That request is
standing approval for the complete bounded delivery sequence: commit only the scoped
files so the tester and reviewer can gate the exact commit; after those gates pass,
push its dedicated codex/ branch, open a linked pull request, post the detailed
testing handoff on the linked GitHub issue, and post the concise Slack follow-up in the
existing thread. Do not pause for another approval between those steps. Recheck and
read back every external write.
Route every contributor- or user-facing draft through the communication manager before an authorized coordinator or operator performs the external write. The communication manager owns wording, evidence mapping, channel fit, privacy, duplication checks, and approval-scope checks; it does not post the message itself.
The communication manager works twice in this route. Before pull-request creation it drafts the title and body from the gated commit. After the GitHub operator creates and reads back the pull request, it uses the real URL to draft the linked-issue handoff and Slack follow-up; the GitHub operator posts the issue handoff and the coordinator posts the Slack paragraph.
The two public responses have distinct positive contracts:
- The GitHub handoff contains the evidence-backed summary plus any clone, checkout, install, health-check, restoration, workload-measurement, and procedural next steps that help the reporter test the exact head.
- The Slack follow-up is one short paragraph: thank the reporter, link the pull request, briefly ask them to try it, and sign it as Pratik's agent. Slack contains no code, commands, clone or install instructions, procedural next steps, test matrix, or long technical summary.
Show full SKILL.md (295 more words)Show less
This standing approval applies only to the linked reporter issue and its existing Slack thread, only after the exact head has the required tester/reviewer evidence and no open finding. It does not authorize merging, releasing, closing, labeling, or requesting hosted review. If delivery is blocked, do not claim a fix or create an unverified pull request.
Two additional narrow standing exceptions remain. When the user explicitly
authorizes checking out, reviewing, or managing pull requests, follow the
one-status-reply-per-PR rule in token-meter-github-ops. When Pratik's agent asked a
contributor to test a pull request and that contributor later reports results, reply
on every existing discussion thread containing those results: thank them, state any
actual next action without inventing a diagnosis or deadline, and sign the message
as Pratik's agent. Omit a follow-up promise when the work is complete. Apply the
same one-short-paragraph Slack contract. These exceptions authorize only the
described replies; other external actions remain gated.
Classification
Produce:
- Requested behavior, acceptance criteria, scope, and non-goals.
- Task class from
.agents/workflow/routing.yaml. - Risk categories from
.agents/workflow/review-policy.yaml. - Whether the low-risk fast path is explicitly eligible, with every required condition accounted for and one allowed change kind selected; uncertainty means it is not eligible.
- Evidence already available and evidence still needed.
- Recommended route and actions that still require approval.
Questions and clarifications normally remain with the coordinator. Diagnosis-only, implementation, verification, review, and GitHub operations move through their declared roles only when needed.
Close the loop
Before drafting a completion response, verify the current workflow state and evidence. State what changed, what was verified, and what remains unverified. Keep the update truthful when work is blocked, local-only, uncommitted, unpushed, or not deployed.
Never include credentials, raw traces, prompts, responses, reasoning, tool contents, account data, or private local paths in a public or shared response.
© 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-intake of splunk/token-meter.
Open the folder on GitHubat commit 4ff456b
Compare with similar skills
Token Meter Intake 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 Intake this skillsplunk/token-meter | 110 | — | ~1.4k | Automated safety check: Warn | MIT | |
| Async Communication Etiquetteaiming-lab/MetaClaw | 3.5k | — | ~224 | Automated safety check: Pass | MIT | |
| Qv PR Minetetherto/qvac | 674 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Report Indicator Changesowid/etl | 158 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Building LoopsPostHog/posthog-foss | 721 | — | ~3.6k | Automated safety check: Pass | MIT | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Qv PR Mine
tetherto/qvac
Show the current user's open PRs across every pod registered under .github/teams/, grouped by merge readiness, with copy-paste Slack ping messages routed to the owning pod's team.
Report Indicator Changes
owid/etl
Draft a short update message to a topic-owner reviewer after landing substantial dataset or chart changes on staging.
- Official
Building Loops
PostHog/posthog-foss
Build a Loop for PostHog Desktop: a workflow that creates an AI task each time its trigger fires, optionally followed by a Slack or email notification with the task's result.
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
Triage
TalAter/annyang
Triage and close GitHub issues on TalAter/annyang. An agent skill from TalAter/annyang.
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 Verification
splunk/token-meter
A skill your agent uses when Token Meter changes or claims need independent source, test, runtime, native, browser, privacy, or platform verification.
Related
Categories
Questions about Token Meter Intake
What does Token Meter Intake do?
A skill your agent uses when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure. Token Meter Intake is an agent skill from splunk/token-meter. Use when a Token Meter Slack or GitHub request needs contextual intake, clarification, triage, acknowledgment, or closure.
When should I use Token Meter Intake?
Token Meter Intake fits situations like: A Token Meter Slack; GitHub request needs contextual intake.
How do I install Token Meter Intake in Claude Code?
Run `npx skills add splunk/token-meter --skill token-meter-intake -a claude-code`. Or copy the skill folder (.agents/skills/token-meter-intake in splunk/token-meter) into .claude/skills/token-meter-intake in your project. Claude Code loads it when a task matches its description.
How do I install Token Meter Intake in Codex?
Run `npx skills add splunk/token-meter --skill token-meter-intake -a codex`. Or copy the skill folder (.agents/skills/token-meter-intake in splunk/token-meter) into .agents/skills/token-meter-intake in your project. Codex loads it when a task matches its description.
Can I use Token Meter Intake 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-intake -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-intake, .gemini/skills/token-meter-intake, .github/skills/token-meter-intake and .opencode/skills/token-meter-intake in your project.
What does Token Meter Intake need to run?
SKILL.md names no scripts, command-line tools or credentials: Token Meter Intake is instructions for the agent only.
Does Token Meter Intake 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 Intake safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): tells the agent its actions are pre-authorized / not to stop for confirmation. Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Token Meter Intake use?
Token Meter Intake 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 Intake use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Intake?
Skills that share tags, products or a category with Token Meter Intake: Async Communication Etiquette (aiming-lab/MetaClaw, 3.5k stars), Qv PR Mine (tetherto/qvac, 674 stars), Report Indicator Changes (owid/etl, 158 stars) and Building Loops (PostHog/posthog-foss, 721 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Token Meter Intake?
splunk (a GitHub organization) maintains it in splunk/token-meter, which has 110 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.