Borrowing it
Nothing to install: this file belongs to SioYooo/RepoGrammar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SioYooo/RepoGrammar/main/.agents/skills/telemetry-and-metrics/SKILL.mdgit clone --depth 1 https://github.com/SioYooo/RepoGrammarWrote 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/sioyooo/repogrammar/telemetry-and-metrics)<a href="https://agentmods.dev/skills/sioyooo/repogrammar/telemetry-and-metrics"><img src="https://agentmods.dev/badge/skills/sioyooo/repogrammar/telemetry-and-metrics.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.1 | $0.00027 | $0.00402 |
| Opus 5 | $0.00014 | $0.00201 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
telemetry-and-metrics 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 7d 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.
What it actually says
Purpose
Keep telemetry privacy-preserving and metric claims auditable.
Trigger conditions
Use when editing repogrammar stats, repogrammar telemetry, telemetry ports,
anonymous telemetry schema, research trace collection, or token metrics.
Required reading
docs/specifications/telemetry.mddocs/specifications/metrics.mddocs/decisions/ADR-0007-safe-install-progress-telemetry.md
Preconditions
- Separate anonymous product telemetry from research trace consent.
- Confirm telemetry is disabled in CI and by environment opt-out.
- Confirm metric kind is one of
MEASURED,DERIVED,ESTIMATED, orCAUSAL_EXPERIMENT.
Step-by-step procedure
- Use the versioned allowlist schema.
- Reject code, paths, repository names, symbols, prompts, query text, evidence text, environment variables, credentials, and raw error messages.
- Use coarse buckets and typed error codes.
- Avoid telemetry latency on MCP calls.
- Honor
REPOGRAMMAR_TELEMETRY=0andDO_NOT_TRACK=1. - Do not report derived context compression as actual token savings.
- Require a comparable baseline before reporting token savings.
Required verification
Run unit tests for consent, environment disablement, schema allowlist, and metric classification.
Documentation updates
Update telemetry and metrics specifications with any schema or claim change.
Commit requirements
Commit code, tests, and docs together. Do not commit local telemetry exports.
Completion report
Report schema version, consent behavior, metric kinds, and any disabled data collection paths.
Failure and rollback handling
If a telemetry field could reveal source, user, repository, or prompt content, remove it before merging.
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.
- 7d ago First seen · 61 lines · 27 tokens per session scan A 7b332862caf1
telemetry-and-metrics is a skill published in the GitHub repository SioYooo/RepoGrammar (0 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 402 once invoked, about $0.0001 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
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.
rate-buildermark
Rate this Claude Code conversation (0-5 scale).
contextlock
Safely inspect a repository through the ContextLock MCP server. Use when exploring, searching, reviewing, or auditing repository files with ContextLock, especially before reading unfamiliar code or when sensitive files and secrets may be present.
clinical-case-report
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…
dcf-valuation
Discounted cash flow valuation and intrinsic value analysis for public companies. Use when the brief asks for DCF, fair value, intrinsic value, price target, undervalued or overvalued analysis, or "what is this company worth?".
digital-eguide
A two-spread digital e-guide preview — page 1 is a cover (display title, author, "What's inside" stats, table of contents teaser); page 2 is a spread (lesson body with pull-quote and a step list). Lifestyle / creator brand tone. Use when the brief asks for an "e-guide", "digital guide", "lookbook", "lead magnet"…