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 skills/neurofoo/agent-skills/eos-usagenpx skills add neurofoo/agent-skills --skill eos-usagegit clone --depth 1 https://github.com/neurofoo/agent-skillsWrote 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/neurofoo/agent-skills/eos-usage)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/eos-usage"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/eos-usage.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.00037 | $0.01187 |
| Opus 5 | $0.00018 | $0.00593 |
| Sonnet 5 | $0.00007 | $0.00237 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
eos-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 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elements of Style: 11 Rules of Usage
Review writing against Strunk & White's 11 elementary rules of usage from Chapter I.
Instructions
Analyze the provided text for grammatical and mechanical errors. Flag specific violations with line numbers or quotes where possible.
Output Format
Text Under Review: [title or brief description]
Usage Review
| # | Rule | Status | Issues Found |
|---|---|---|---|
| 1 | Form possessive singular with 's | Pass/Needs Work/N/A | [issues] |
| 2 | Use serial comma | Pass/Needs Work/N/A | [issues] |
| 3 | Enclose parenthetic expressions in commas | Pass/Needs Work/N/A | [issues] |
| 4 | Comma before conjunction + independent clause | Pass/Needs Work/N/A | [issues] |
| 5 | No comma splice | Pass/Needs Work/N/A | [issues] |
| 6 | No sentence fragments | Pass/Needs Work/N/A | [issues] |
| 7 | Use colon to introduce lists/appositives | Pass/Needs Work/N/A | [issues] |
| 8 | Use dash for abrupt breaks | Pass/Needs Work/N/A | [issues] |
| 9 | Subject-verb agreement | Pass/Needs Work/N/A | [issues] |
| 10 | Proper pronoun case | Pass/Needs Work/N/A | [issues] |
| 11 | Dangling modifiers | Pass/Needs Work/N/A | [issues] |
Errors Found
Rule 5: Comma Splices
| Location | Error | Correction |
|---|---|---|
| [line/quote] | "It is cold, we should go inside" | "It is cold; we should go inside" OR "It is cold, so we should go inside" |
Rule 6: Sentence Fragments
| Location | Fragment | Suggested Fix |
|---|---|---|
| [line/quote] | [fragment] | [complete sentence] |
Rule 11: Dangling Modifiers
| Location | Error | Correction |
|---|---|---|
| [line/quote] | "Walking down the street, the trees were beautiful" | "Walking down the street, I noticed the beautiful trees" |
Rule Reference
- Form the possessive singular by adding 's — Charles's friend, Burns's poems, the witch's malice. Exceptions: ancient proper names ending in -es or -is (Jesus', Moses'), and common idioms (for conscience' sake).
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 · 106 lines · 37 tokens per session scan A 383db1056986
eos-usage is a skill published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 1,187 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…