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.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/common/common-telemetry/SKILL.mdAs your final step in any SDLC workflow (or when a user explicitly requests session cost):
get_session_cost tool provided by the agent-skills-standard MCP server.workflow, model, token counts, cache/reasoning usage, and per-1M token rates when the host runtime exposes them. Set slug (feature/workspace name) and outcome (terminal feature_status) when this call finalizes a workflow, so the telemetry log can attribute cost per feature.costSource: "host" yourself — that value is reserved for the runtime's own telemetry adapter (buildSessionCostRequest). If you type numbers by hand, omit costSource so the tool reports them as agent-estimate, never host.get_session_cost mark cost provenance as unavailable — never fabricate a number or a $0.00 total.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.
unknown or unavailable. Never coerce missing values to 0 or calculate $0.00 totals from partial data.unknown or partial. Do not report exact cost figures without complete rate coverage.completed, failed, or blocked.mcp/src/services/WorkflowTelemetry.ts to:
get_session_cost payloadEnsure 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] |
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.00 or any other placeholder cost when get_session_cost reports unavailable; render the provenance value as-is.
No zero-coercion of missing metrics: Missing token or rate fields must stay unknown or unavailable; 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.
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
Call get_session_cost when the host exposes it, then append the Markdown table to artifacts/session-cost.md.
Cost Provenance: host, agent-estimate, unavailable
Telemetry & Cost Reporting
HoangNguyen0403/agent-skills-standard
cd1e988
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.