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/rohitbind123/claude-setup/configure-eccnpx skills add RohitBind123/claude-setup --skill configure-eccgit clone --depth 1 https://github.com/RohitBind123/claude-setupWrote 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/rohitbind123/claude-setup/configure-ecc)<a href="https://agentmods.dev/skills/rohitbind123/claude-setup/configure-ecc"><img src="https://agentmods.dev/badge/skills/rohitbind123/claude-setup/configure-ecc.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.00038 | $0.03246 |
| Opus 5 | $0.00019 | $0.01623 |
| Sonnet 5 | $0.00008 | $0.00649 |
| Haiku 4.5 | $0.00004 | $0.00325 |
Grade D, and why
configure-ecc scanned grade D with 2 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -rn "~/.claude/" $TARGET/skills/ $TARGET/rules/ Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/everything-claude-code This is a copy
100% identical to configure-ecc — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Everything Claude Code (ECC)
An interactive, step-by-step installation wizard for the Everything Claude Code project. Uses AskUserQuestion to guide users through selective installation of skills and rules, then verifies correctness and offers optimization.
When to Activate
- User says "configure ecc", "install ecc", "setup everything claude code", or similar
- User wants to selectively install skills or rules from this project
- User wants to verify or fix an existing ECC installation
- User wants to optimize installed skills or rules for their project
Prerequisites
This skill must be accessible to Claude Code before activation. Two ways to bootstrap:
- Via Plugin:
/plugin install everything-claude-code— the plugin loads this skill automatically - Manual: Copy only this skill to
~/.claude/skills/configure-ecc/SKILL.md, then activate by saying "configure ecc"
Step 0: Clone ECC Repository
Before any installation, clone the latest ECC source to /tmp:
rm -rf /tmp/everything-claude-code
git clone https://github.com/affaan-m/everything-claude-code.git /tmp/everything-claude-code
Set ECC_ROOT=/tmp/everything-claude-code as the source for all subsequent copy operations.
If the clone fails (network issues, etc.), use AskUserQuestion to ask the user to provide a local path to an existing ECC clone.
Step 1: Choose Installation Level
Use AskUserQuestion to ask the user where to install:
Question: "Where should ECC components be installed?"
Options:
- "User-level (~/.claude/)" — "Applies to all your Claude Code projects"
- "Project-level (.claude/)" — "Applies only to the current project"
- "Both" — "Common/shared items user-level, project-specific items project-level"
Store the choice as INSTALL_LEVEL. Set the target directory:
- User-level:
TARGET=~/.claude - Project-level:
TARGET=.claude(relative to current project root) - Both:
TARGET_USER=~/.claude,TARGET_PROJECT=.claude
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.
- 3d ago First seen · 327 lines · 38 tokens per session scan D 5f3506f77baf
configure-ecc is a skill published in the GitHub repository RohitBind123/claude-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 3,246 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). It is 100% identical to configure-ecc, differing in 0 lines, and is treated as a copy.
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…