common-telemetry
Periodically refreshed mirror of agents, skills, prompts and instruction files from public repositories.
Install / Use
npx skills add gabrielmoreira/agent-skills-mirror --skill common-telemetryInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of common-telemetry
common-telemetry scores 54/100 on our quality scale, 2706th of 2,790 Automation skills we index.
Its SKILL.md is 5.2 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-11-12 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-13. Automated pattern scan on 2026-11-13. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
common-telemetry compared with similar skills
All 4 of these similar skills score higher than common-telemetry; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| common-telemetry (this skill)by gabrielmoreira | 54 | 0 | — | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install common-telemetry?
- Run
npx skills add gabrielmoreira/agent-skills-mirror --skill common-telemetry. The install tabs above show the steps for each supported agent. - Which AI agents does common-telemetry work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is common-telemetry safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is common-telemetry still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubname: common-telemetry description: Enforce session-cost telemetry and execution-metadata reporting. Use when explicitly invoking get_session_cost, reporting token/cost usage, applying telemetry or cost guidance during a workflow handoff, or writing artifacts/session-cost.md at a workflow terminal state. metadata: triggers: files: [] keywords: - token cost - token usage - session telemetry - cost report
Telemetry & Cost Reporting
Priority: P2 (MEDIUM)
1. Finalizing a Workflow
As your final step in any SDLC workflow (or when a user explicitly requests session cost):
- Call the
get_session_costtool provided by the agent-skills-standard MCP server. - Pass
workflow,model, token counts, cache/reasoning usage, and per-1M token rates when the host runtime exposes them. Setslug(feature/workspace name) andoutcome(terminalfeature_status) when this call finalizes a workflow, so the telemetry log can attribute cost per feature. - Never set
costSource: "host"yourself — that value is reserved for the runtime's own telemetry adapter (buildSessionCostRequest). If you type numbers by hand, omitcostSourceso the tool reports them asagent-estimate, neverhost. - If token counts are unavailable, report MCP-observed telemetry and let
get_session_costmark cost provenance asunavailable— never fabricate a number or a$0.00total. - Append a Markdown table containing the usage metrics to
artifacts/session-cost.md.
When asked which artifact to use, always name both artifacts/session-cost.md and get_session_cost; if the host does not expose the helper, say so explicitly while retaining the artifact requirement.
2. Accounting Boundaries & Lineage Semantics
- Missing ≠ Zero: When metric fields or token counts are missing from runtime events, treat them as
unknownorunavailable. Never coerce missing values to0or calculate$0.00totals from partial data. - Partial Lineage & Incomplete Rates: If pricing rates, cache rates, reasoning rates, or token lineage across subagents are incomplete, mark total cost as
unknownorpartial. Do not report exact cost figures without complete rate coverage. - Subagent & Worker Cost Scope: Shared parent orchestration costs and worker-only slices represent partial task scope. Never claim subagent-only costs as full-task totals or assert net savings without measured baselines.
- Discovery Lifecycle Distinctness: Do not conflate resource state transitions. Catalog discovery (skills listed/indexed) ≠ body fetched (skill markdown loaded) ≠ delivered to agent context ≠ actively used/applied in generation. Persisted telemetry must not assert usage when only discovery or delivery occurred.
- Efficacy & Savings Claims: Never claim model efficacy uplift or token savings without qualified, independently reproducible measurement evidence against an authoritative baseline.
3. Host Runtime Contract
- This skill defines the telemetry contract; it does not collect provider billing data by itself.
- The host runtime or orchestrator must trigger the final telemetry call when the workflow reaches a terminal state such as
completed,failed, orblocked. - The host may use a reusable helper such as
mcp/src/services/WorkflowTelemetry.tsto:- decide when telemetry should fire
- build the
get_session_costpayload - pass prompt, cache, reasoning, pricing, and other runtime cost fields when available
4. Telemetry Format
Ensure the artifacts/session-cost.md or the output template ## Cost Report follows this structure, copying the get_session_cost output verbatim rather than re-deriving values:
| Metric | Value |
| ------------------------ | ------------------------------------------------------- |
| Tool Calls | [from get_session_cost] |
| Skills Loaded | [from get_session_cost] |
| Workflows Loaded | [from get_session_cost] |
| Prompt Tokens | [from get_session_cost, or "unavailable" if not exposed] |
| Cached Prompt Tokens | [from get_session_cost, or "unavailable" if not exposed] |
| Completion Tokens | [from get_session_cost, or "unavailable" if not exposed] |
| Reasoning Tokens | [from get_session_cost, or "unavailable" if not exposed] |
| Other Runtime Cost | [from get_session_cost, or "unavailable" if not exposed] |
| Cost Provenance | host | agent-estimate | unavailable |
| Estimated Cost | [from get_session_cost, or "unavailable" — never $0.00] |
Anti-Patterns
-
No skipping the telemetry step: Always include the Cost Report at the end of the execution if mandated by the workflow.
-
No fabricated numbers: Never invent a
$0.00or any other placeholder cost whenget_session_costreportsunavailable; render the provenance value as-is. -
No zero-coercion of missing metrics: Missing token or rate fields must stay
unknownorunavailable; never coerce to 0. -
No conflating catalog discovery with usage: Listing a skill or fetching its markdown does not imply it was used in model generation.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
