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-compositionnpx skills add neurofoo/agent-skills --skill eos-compositiongit 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-composition)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/eos-composition"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/eos-composition.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.01215 |
| Opus 5 | $0.00018 | $0.00607 |
| Sonnet 5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
eos-composition 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 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.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elements of Style: 11 Composition Principles
Review writing against Strunk & White's 11 elementary principles of composition from Chapter II.
Instructions
Analyze the provided text for structural and compositional issues. Provide specific examples with before/after suggestions where improvements are needed.
Output Format
Text Under Review: [title or brief description]
Composition Review
| # | Principle | Status | Notes |
|---|---|---|---|
| 1 | Choose a suitable design and stick to it | Pass/Needs Work/N/A | [feedback] |
| 2 | Make the paragraph the unit of composition | Pass/Needs Work/N/A | [feedback] |
| 3 | Use the active voice | Pass/Needs Work/N/A | [feedback] |
| 4 | Put statements in positive form | Pass/Needs Work/N/A | [feedback] |
| 5 | Use definite, specific, concrete language | Pass/Needs Work/N/A | [feedback] |
| 6 | Omit needless words | Pass/Needs Work/N/A | [feedback] |
| 7 | Avoid a succession of loose sentences | Pass/Needs Work/N/A | [feedback] |
| 8 | Express coordinate ideas in parallel form | Pass/Needs Work/N/A | [feedback] |
| 9 | Keep related words together | Pass/Needs Work/N/A | [feedback] |
| 10 | In summaries, keep to one tense | Pass/Needs Work/N/A | [feedback] |
| 11 | Place the emphatic words at the end | Pass/Needs Work/N/A | [feedback] |
Detailed Findings
Principle 3: Active Voice
Passive voice found:
| Original | Suggested |
|---|---|
| [passive construction] | [active alternative] |
Principle 4: Positive Form
Negative constructions found:
| Original | Suggested |
|---|---|
| "He was not very often on time" | "He usually arrived late" |
Principle 6: Omit Needless Words
Wordy phrases found:
| Original | Suggested |
|---|---|
| "the reason why is that" | "because" |
| "in spite of the fact that" | "although" |
| "the fact that he had arrived" | "his arrival" |
Principle 8: Parallel Form
Non-parallel constructions:
| Original | Suggested |
|---|---|
| [non-parallel] | [parallel version] |
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.
- 5d ago First seen · 122 lines · 37 tokens per session scan A 214e1241a265
eos-composition 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,215 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…