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/eigenwise/eigenwise-toolshed/add-rulenpx skills add Eigenwise/eigenwise-toolshed --skill add-rulegit clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshedWrote 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/eigenwise/eigenwise-toolshed/add-rule)<a href="https://agentmods.dev/skills/eigenwise/eigenwise-toolshed/add-rule"><img src="https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/add-rule.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.00036 | $0.01932 |
| Opus 5 | $0.00018 | $0.00966 |
| Sonnet 5 | $0.00007 | $0.00386 |
| Haiku 4.5 | $0.00004 | $0.00193 |
Grade A, and why
add-rule 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Rule
Turn a request like "always run the linter before committing" or "when editing *.tsx, prefer
function components" into a rule in the project's live-rules file. The plugin's hooks inject each
rule automatically, at the moment it applies, so the user does not have to remember to paste it.
Read references/rule-format.md for the full frontmatter spec and references/example-rules.md for
ready-to-adapt examples before writing your first rule.
Do not edit CLAUDE.md. The hooks are the only delivery mechanism; rules live entirely in the
live-rules file.
Atomic storage
For new workspaces, keep each rule in .claude/live-rules/rules/<stable-name>.md. After adding or editing a rule, run the plugin-owned sync command from the project root:
node "${CLAUDE_PLUGIN_ROOT}/scripts/sync-atomic-rules.js" --project "${CLAUDE_PROJECT_DIR}"
It derives every manifest hash and metadata field from the rule files, validates a stable read, and atomically replaces only the generated manifest under a writer lock. Rule files remain authoritative and are never rewritten by sync. Never author or repair .claude/live-rules/manifest.json by hand. If sync fails, fix the exact file it names, then run the same command again. Keep the old .claude/live-rules.md format only for existing projects until it has been migrated.
Step 1 - Find the rules file
New workspaces use the atomic directory described above. Existing projects may still have one Markdown file. Resolve that legacy file in this order when migrating or maintaining an existing project:
- If the
LIVE_RULES_PATHenvironment variable is set (commonly in.claude/settings.jsonunderenv), that path is the file (it may be project-relative, absolute, or~-relative). - Otherwise it is
.claude/live-rules.mdat the project root.
If the file does not exist yet, create it with a short title line so a teammate opening it understands what it is:
# Live rules
These rules are re-injected into Claude's context every turn (and before relevant edits) so they stay
in front of the model. Each rule below is a frontmatter block plus body. Edit freely; changes take
effect on the next prompt. Commit this file so the team shares the rules.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 144 lines · 36 tokens per session scan A 7aadd1505ab8
add-rule is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (37 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,932 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…