setup

setup is a skill for Claude Code, Codex from eltonylfgi-blip/claude-code-usage-guard. It costs 110 tokens per session (849 once invoked), scanned B, original, MIT.

A setup procedure that connects usage-guard to Claude Code's status line so it can read your actual five-hour and weekly plan limits.

In plain words
What is it for?
Use it after installing usage-guard, when enabling real quota readings, connecting the status line, or fixing a usage screen that lacks the real quota section.
Why use it?
Without this one-time connection, usage-guard cannot see the real limits and may stay silent or show only an estimate.

Skill for Claude CodeCodex

Part of the usage-guard plugin — 2 skills, 2 hooks shipped together

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.

agentmods
npx agentmods add skills/eltonylfgi-blip/claude-code-usage-guard/setup
Any agent
npx skills add eltonylfgi-blip/claude-code-usage-guard --skill setup
Clone the repo
git clone --depth 1 https://github.com/eltonylfgi-blip/claude-code-usage-guard

Made for: Claude Code, Codex.

Or install usage-guard, the plugin that ships this one along with the rest of its 2 skills, 2 hooks.

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 setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/eltonylfgi-blip/claude-code-usage-guard/setup.svg)](https://agentmods.dev/skills/eltonylfgi-blip/claude-code-usage-guard/setup)
Your own site
<a href="https://agentmods.dev/skills/eltonylfgi-blip/claude-code-usage-guard/setup"><img src="https://agentmods.dev/badge/skills/eltonylfgi-blip/claude-code-usage-guard/setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 849 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00110 $0.00849
Opus 5 $0.00055 $0.00425
Sonnet 5 $0.00022 $0.00170
Haiku 4.5 $0.00011 $0.00085

Measured 5d ago against content hash 2908c39be68f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

setup scanned grade B with 1 finding 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 5d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

2. **Open the user's settings.** Path: `~/.claude/settings.json` (Windows: `%USERPROFILE%\.claude\settings.json`). If it does not exist, create it as `{}`. **Always back it up first** (copy to `settings.json.bak`) before
skills/setup/SKILL.md · 40 lines

How it starts

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

usage-guard setup

Most people install usage-guard but never wire the one-time status-line shim, so the real plan quota never turns on and the guard stays silent. This skill does that wiring for them with as little friction as possible. Prefer doing the edit for the user (with a backup) over just printing instructions — the whole point is to remove the manual step.

Steps

  1. Locate the installed status-line shim. It lives under the user's Claude plugins dir. Run this (works on macOS, Linux and Windows):

    node -e "const fs=require('fs'),p=require('path'),os=require('os');const root=p.join(os.homedir(),'.claude','plugins');let hit;(function w(d){let es;try{es=fs.readdirSync(d,{withFileTypes:true})}catch(e){return}for(const x of es){if(x.name==='node_modules'||x.name==='.git')continue;const f=p.join(d,x.name);if(x.isDirectory())w(f);else if(x.name==='usage-guard-statusline.mjs')hit=f}})(root);console.log(hit||'NOT_FOUND')"
    

    If it prints NOT_FOUND, tell the user to run /plugin install usage-guard@cc-guard first, then retry.

  2. Open the user's settings. Path: ~/.claude/settings.json (Windows: %USERPROFILE%\.claude\settings.json). If it does not exist, create it as {}. Always back it up first (copy to settings.json.bak) before editing.

  3. Wire the statusLine, preserving any existing one:

    • If there is NO existing statusLine, set it to run the shim directly:
      "statusLine": { "type": "command", "command": "node \"<ABSOLUTE_PATH_FROM_STEP_1>\"" }
      
    • If a statusLine.command already exists, do NOT clobber it — chain it through the env var so their line still renders after the snapshot:
      "statusLine": { "type": "command", "command": "USAGE_GUARD_STATUSLINE='<their existing command>' node \"<ABSOLUTE_PATH_FROM_STEP_1>\"" }
      
      (On Windows the env var is set in the wrapping shell — see TUTORIAL.md for the .cmd wrapper.)
  4. Confirm in one line. Tell the user it's wired, and that after their next couple of Claude Code messages, /usage-guard:usage will start with a real Real plan quota block. Note that real quota only appears on Claude.ai Pro/Max sessions and only after the first API response; until then the weighted fallback is used.

Read the full file on GitHub · 40 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. 5d ago First seen · 40 lines · 110 tokens per session scan B 2908c39be68f

Subscribe to this mod's changes

setup is a skill published in the GitHub repository eltonylfgi-blip/claude-code-usage-guard (3 stars, last pushed today), licensed MIT. It adds 110 tokens to every session and 849 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.