skills/common/common-telemetry/SKILL.md
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.
npx skillsauth add hoangnguyen0403/agent-skills-standard common-telemetryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
As 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.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.
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:
| Metric | Value | | ------------------------ | ------------------------------ | | Tool Calls | [from get_session_cost] | | Skills Loaded | [from get_session_cost] | | Workflows Loaded | [from get_session_cost] | | Prompt Tokens | [from your platform telemetry] | | Cached Prompt Tokens | [from your platform telemetry] | | Completion Tokens | [from your platform telemetry] | | Reasoning Tokens | [from your platform telemetry] | | Other Runtime Cost | [tooling/provider extras] | | Estimated Cost | $0.00 |
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.
Telemetry & Cost Reporting
testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.