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 skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-telemetry
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:
get_session_cost when the host exposes it, then append the Markdown table to artifacts/session-cost.md.Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take hoangnguyen0403/common-telemetry from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.