Common Telemetry
Enforce session-cost telemetry and execution-metadata reporting.
Install
npx skills add HoangNguyen0403/agent-skills-standard --skill common-telemetry -g -a claude-code -y- Repository
- HoangNguyen0403/agent-skills-standard582
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,314 tokens
- Runs scripts
- No, instructions only
What it does
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.
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.
