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.
npx skills add YuriNachos/claude-scope --skill scopegit clone --depth 1 https://github.com/YuriNachos/claude-scopeWrote 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.
[](https://agentmods.dev/skills/yurinachos/claude-scope/scope)<a href="https://agentmods.dev/skills/yurinachos/claude-scope/scope"><img src="https://agentmods.dev/badge/skills/yurinachos/claude-scope/scope/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.
<a href="https://agentmods.dev/skills/yurinachos/claude-scope/scope"><img src="https://agentmods.dev/badge/skills/yurinachos/claude-scope/scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01442 |
| Opus 5.5 | $0.00013 | $0.00577 |
| Sonnet 5.5 | $0.00007 | $0.00288 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
scope 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Scope Configuration Skill
Help users configure their claude-scope status line widgets.
Configuration Path
Config file: ~/.claude-scope/config.json
Workflow
- Read current config from
~/.claude-scope/config.json - Understand what the user wants to change
- Edit the config using the Edit tool
- Confirm changes to the user
Changes apply automatically on the next status line render cycle.
Quick Reference
Config Structure
{
"version": "1.0.0",
"theme": "monokai",
"lines": {
"0": [{ "id": "model", "style": "balanced", "colors": {...} }],
"1": [{ "id": "git", "style": "balanced", "colors": {...} }]
}
}
linesis an object where keys are line numbers ("0", "1", "2", etc.)- Each line contains an array of widget configurations
- Widgets render left-to-right within each line
- Empty lines should be empty arrays
[]
Available Widgets (16)
| Widget ID | Description | Typical Line |
|---|---|---|
cwd |
Current working directory | 0 |
model |
Claude model name (e.g., "Claude Opus 4.5") | 0 |
context |
Context window usage with progress bar | 0 |
cost |
Session cost in USD | 0 |
duration |
Session elapsed time | 0 |
lines |
Lines added/removed during session | 0 |
git |
Current git branch and changes | 1 |
git-tag |
Latest git tag | 1 |
config-count |
CLAUDE.md, rules, MCPs, hooks counts | 1 |
cache-metrics |
Cache hit rate and cost savings | 1 |
active-tools |
Running and completed Claude tools | 2 |
dev-server |
Dev server status (Nuxt, Next, Vite) | 2 |
docker |
Docker container count and status | 2 |
sysmon |
System metrics (CPU, RAM, Disk, Network) | 3 |
poker |
Random poker hand (easter egg) | 4 |
empty-line |
Blank separator line | any |
Available Themes (17)
monokai (default), nord, dracula, catppuccin-mocha, tokyo-night,
vscode-dark-plus, github-dark-dimmed, dusty-sage, muted-gray,
slate-blue, professional-blue, rose-pine, semantic-classic,
solarized-dark, one-dark-pro, cyberpunk-neon, gray
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.
- 1mo ago First seen · 171 lines · 33 tokens per session scan A 74d5a7ace467
scope is a skill published in the GitHub repository YuriNachos/claude-scope (11 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,442 once invoked, about $0.0001 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-31.
Other skills, from other repositories
create-mascot-pack
Create or modify pixel-art mascot packs for claude-code-mascot-statusline plugin. Use when: creating a new character pack from scratch, modifying existing pack sprites, fixing visual issues in half-block rendering, iterating on sprite design, or adding new states to a pack. Triggers: "create pack", "new mascot"…
hcom-agent-messaging
Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom or troubleshooting.
gap-analyzer
Compares a CLI's implemented commands against its APP.md API map and traffic-analysis.json to find missing endpoints, incomplete CRUD, dead client methods, and priority gaps. Runs as the mandatory first step of /cli-anything-web:refine and as an optional pre-review scan in standards.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.