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 agentmods add instructions/viganogabriele/agent-usage-plus/claude-mdgit clone --depth 1 https://github.com/viganogabriele/agent-usage-plusWrote 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/instructions/viganogabriele/agent-usage-plus/claude-md)<a href="https://agentmods.dev/instructions/viganogabriele/agent-usage-plus/claude-md"><img src="https://agentmods.dev/badge/instructions/viganogabriele/agent-usage-plus/claude-md.svg" alt="Measured on agentmods" 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 | $0.00637 | $0.00637 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
agent-usage-plus CLAUDE.md 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Usage Plus: Claude Code notes
This is an Omarchy/Quickshell plugin. Start with AGENTS.md, then read the
relevant contract or collector documentation before editing data paths.
Do
- Keep UI, logic and collectors separate: test pure logic in
logic/; make collector records followdocs/collector-contract.md. - Treat missing credentials as a normal provider state with a direct fix, not as an absent provider or a raw process error.
- Use
npm test, the Qt 6qmllintcommand inAGENTS.md, and manifest validation for every code change; also run the Python suite incollectors/tests/when a change touchescollectors/— it is not part ofnpm test. - Restart the shell for every live QML check. Do not rely on hot reload or
rescanPlugins. - Verify the real panel after UI changes, especially sizing, scroll speed, overflow, empty/auth states, and bar marks at actual bar scale.
- Double-JSON-encode any array-valued setting before writing it with
omarchy bar set ... --json(JSON.stringify(JSON.stringify(arr)), parsed back with a guardedJSON.parseon read) — a bare multi-element JSON array value makes that command fail every time. See AGENTS.md andproviderOrderin Main.qml. - Before treating a missing notification as a bug, check Omarchy's own Do Not Disturb flag and notification history (paths in AGENTS.md) — a successful send with DND on produces no visible popup by design.
Do not
- Do not access credentials, directly edit Omarchy shell settings, push, or create pull requests without explicit user approval.
- Do not use raster provider logos or assume panel icon sizing also works in
the bar. Always set
sourceSize(×Screen.devicePixelRatio) on mark images, or they read as soft/blurry. - Keep Omarchy theme behavior intact: live surface/foreground/urgent colors,
light/default provider marks selected from the live bar foreground, and the
deliberate fixed amber warning color (
#F2B705). - Keep provider response handling bounded and fail-closed: parse at most the collector limit, surface auth/endpoint errors explicitly, and never log upstream bodies or credentials.
- Do not turn a collector failure into a silent blank state.
- Do not add a hardcoded cap on how many providers can appear in the bar. The limit is whatever the person has configured (Fixed count + Cycle slots), which is already bounded by how many providers exist to configure — see AGENTS.md.
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.
- 4d ago First seen · 53 lines · 637 tokens per session scan A 4034b293582a
agent-usage-plus CLAUDE.md is an instructions file published in the GitHub repository viganogabriele/agent-usage-plus (2 stars, last pushed yesterday), licensed MIT. It adds 637 tokens to every session, about $0.0032 per session on Opus 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.