claude-code-usage

claude-code-usage is a skill for Claude Code, Codex from ComeOnOliver/skillshub. It costs 55 tokens per session (2,222 once invoked), scanned A, original, MIT.

A set of working rules for Claude Code, an AI coding assistant used from a command line. It explains how to organize tasks, manage conversation context, and provide useful information when asking for code changes or debugging help.

In plain words
What is it for?
Use it to decide when to work directly, when to make a plan for a large or multi-file change, when to clear the conversation, and what details to include in a debugging request.
Why use it?
It reduces mistakes caused by mixing unrelated work, carrying too much old context, or starting large changes without an agreed approach. It also gives clearer ways to report errors and request analysis.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions Claude Code.

Good fit Use it to decide when to work directly, when to make a plan for a large or multi-file change, when to clear the conversation, and what details to include in a debugging request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/comeonoliver/skillshub/claude-code-usage
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ComeOnOliver/skillshub --skill claude-code-usage
Clone the repo
git clone --depth 1 https://github.com/ComeOnOliver/skillshub

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for claude-code-usage

README.md
[![agentmods](https://agentmods.dev/badge/skills/comeonoliver/skillshub/claude-code-usage/github.svg)](https://agentmods.dev/skills/comeonoliver/skillshub/claude-code-usage)
Your own site
<a href="https://agentmods.dev/skills/comeonoliver/skillshub/claude-code-usage"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/claude-code-usage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for claude-code-usage

Your own site · 80×15
<a href="https://agentmods.dev/skills/comeonoliver/skillshub/claude-code-usage"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/claude-code-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.02222
Opus 5.5 $0.00022 $0.00889
Sonnet 5.5 $0.00011 $0.00444
Haiku 4.5 $0.00006 $0.00222

Measured 1mo ago against content hash dabbce520495, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

claude-code-usage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/0xlayerghost/solidity-agent-kit/claude-code-usage/SKILL.md · 224 lines

How it starts

The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Code Best Practices

Language Rule

  • Always respond in the same language the user is using. If the user asks in Chinese, respond in Chinese. If in English, respond in English.

Context Management Rules

Rule Why
One window = one task Mixing tasks pollutes context and degrades output quality
Use /clear over /compact Clean start is more reliable than compressed context
/clear after complex tasks Prevents old context from interfering with new work
Copy key info to new windows Don't rely on context persistence — paste critical details

Task Execution Strategy

Task Type Recommended Approach
Small bug fix (few lines) Describe directly, let Claude modify in-place
Large feature / refactor /plan → review approach → /clear → paste plan → execute step by step
Multi-file changes Must use /plan workflow — never modify multiple files without a plan
Code analysis / learning Ask Claude to analyze directly — no plan needed
Debugging Provide error message + file path + relevant code — ask for root cause

Prompt Techniques

Do This

  • Give specific paths: "Modify the _transfer function in src/MyToken.sol"
  • Give examples: "Input: 100 tokens, Expected: 95 tokens after 5% fee"
  • Set boundaries: "Only modify this function, don't touch other code"
  • Reference tests: "The fix should make test_transfer_feeDeduction pass"

Avoid This

  • Vague references: "Modify that transfer function" — which one? Where?
  • Open-ended requests without constraints: "Make it better"
  • Multiple unrelated tasks in one message

Ambiguity Resolution — When Instructions Are Unclear

When a user instruction is vague, open-ended, or could be interpreted in multiple ways, do NOT guess and proceed. Proactively analyze the instruction and present all possible interpretations for the user to confirm before taking action.

Trigger Conditions

Read the full file on GitHub · 224 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 224 lines · 55 tokens per session scan A dabbce520495

Subscribe to this mod's changes

claude-code-usage is a skill published in the GitHub repository ComeOnOliver/skillshub (64 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 2,222 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.