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 skills add ychampion/cskill-agents --skill telemetry-sanitized-skill-invocationgit clone --depth 1 https://github.com/ychampion/cskill-agentsWrote 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/skills/ychampion/cskill-agents/telemetry-sanitized-skill-invocation)<a href="https://agentmods.dev/skills/ychampion/cskill-agents/telemetry-sanitized-skill-invocation"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/telemetry-sanitized-skill-invocation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ychampion/cskill-agents/telemetry-sanitized-skill-invocation"><img src="https://agentmods.dev/badge/skills/ychampion/cskill-agents/telemetry-sanitized-skill-invocation.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.00569 |
| Opus 5 | $0.00018 | $0.00284 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
telemetry-sanitized-skill-invocation 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 8d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Telemetry Sanitized Skill Invocation
Domain: tool-orchestration
Trigger: Use when SkillTool emits tengu_skill_tool_invocation so built-in commands, remote MCP skills, and forked executions are logged without exposing command strings in open analytics tables.
Source Pattern: Distilled from reviewed tool-loop and result-shaping patterns.
Core Method
Before executing any skill, compute whether the command is built-in, bundled, official marketplace, or custom and pass the sanitized value as command_name while storing the actual skill name under _PROTO_skill_name to satisfy both privacy and auditability. Add contextual metadata such as execution_context (inline, forked, remote), query_depth, parent_agent_id, and plugin fields when applicable, and wrap remote canonical invocations or discovered skills with additional flags so downstream dashboards know the skill source without revealing user-generated text. Emit separate telemetry for inline/forked/remote flows so metrics can split by execution path while normalizing the skill name for aggregated reporting.
Key Rules
- Derive
sanitizedCommandNameascommandNamefor built-in/bundled/official skills and fall back to'custom'for user-authored commands; log the actual name only in_PROTO_skill_nameto keep BigQuery columns safe. - Always include
execution_context('inline','forked','remote') plusinvocation_trigger(nested vs proactive) andquery_depthso telemetry consumers understand the runtime scenario. - When a plugin skill is involved, add both
_PROTO_plugin_nameand the sanitizedplugin_name/plugin_repositoryfields along with marketplace metadata to enable plugin-level analytics without leaking repository URLs. - For remote MCP skills, emit
is_remote,was_discovered, and cached load info (latency, cache hit) so telemetry can diagnose discovery performance without exposing the raw prompt body.
Example Application
Use this skill to log any slash command invocation, ensuring that a cloned forked review or remote_skill call still records an execution_context flag plus proper naming sanitization for consumption by privacy-sensitive dashboards.
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.
- 8d ago First seen · 28 lines · 36 tokens per session scan A 693fd45f137b
telemetry-sanitized-skill-invocation is a skill published in the GitHub repository ychampion/cskill-agents (36 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 569 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-09-03.
Other skills, from other repositories
grape
Use Grape MCP for Codex context continuity in coding repositories. Use when a task needs repeated-turn context, omitted context restore, stale-context checks, invalidation checks, or safe continuity across branch and dirty-worktree changes.
review
Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
brainstorm
Explore ambiguous or early-stage ideas interactively — tracks wish-readiness and crystallizes into a design for wish.
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
genie
Entry point for Genie operations — routes bug reports, questions, and operational commands, resumes existing lifecycle state, and orchestrates work that needs durable planning or coordination. Other ordinary requests bypass the lifecycle with a one-line notice unless the user asks for Genie.