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/siniyayousuf/everything_claudecode/everything-claude-codenpx skills add SiniyaYousuf/everything_claudecode --skill everything-claude-codegit clone --depth 1 https://github.com/SiniyaYousuf/everything_claudecodeWrote 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/siniyayousuf/everything_claudecode/everything-claude-code)<a href="https://agentmods.dev/skills/siniyayousuf/everything_claudecode/everything-claude-code"><img src="https://agentmods.dev/badge/skills/siniyayousuf/everything_claudecode/everything-claude-code.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.00000 | $0.00751 |
| Opus 5 | $0.00000 | $0.00376 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
everything-claude-code 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.
This is a copy
100% identical to everything-claude-code — 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Everything Claude Code
Use this skill when working inside the everything-claude-code repository and you need repo-specific guidance instead of generic coding advice.
Optional companion instincts live at .claude/homunculus/instincts/inherited/everything-claude-code-instincts.yaml for teams using continuous-learning-v2.
When to Use
Activate this skill when the task touches one or more of these areas:
- cross-platform parity across Claude Code, Cursor, Codex, and OpenCode
- hook scripts, hook docs, or hook tests
- skills, commands, agents, or rules that must stay synchronized across surfaces
- release work such as version bumps, changelog updates, or plugin metadata updates
- continuous-learning or instinct workflows inside this repository
How It Works
1. Follow the repo's development contract
- Use conventional commits such as
feat:,fix:,docs:,test:,chore:. - Keep commit subjects concise and close to the repo norm of about 70 characters.
- Prefer camelCase for JavaScript and TypeScript module filenames.
- Use kebab-case for skill directories and command filenames.
- Keep test files on the existing
*.test.jspattern.
2. Treat the root repo as the source of truth
Start from the root implementation, then mirror changes where they are intentionally shipped.
Typical mirror targets:
.cursor/.codex/.opencode/.agents/
Do not assume every .claude/ artifact needs a cross-platform copy. Only mirror files that are part of the shipped multi-platform surface.
3. Update hooks with tests and docs together
When changing hook behavior:
- update
hooks/hooks.jsonor the relevant script inscripts/hooks/ - update matching tests in
tests/hooks/ortests/integration/ - update
hooks/README.mdif behavior or configuration changed - verify parity for
.cursor/hooks/and.opencode/plugins/when applicable
4. Keep release metadata in sync
When preparing a release, verify the same version is reflected anywhere it is surfaced:
package.json.claude-plugin/plugin.json.claude-plugin/marketplace.json.opencode/package.json- release notes or changelog entries when the release process expects them
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 · 98 lines · 0 tokens per session scan A 7559420136e1
everything-claude-code is a skill published in the GitHub repository SiniyaYousuf/everything_claudecode (14 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 751 tokens. A static security scan graded it A with 0 findings. It is 100% identical to everything-claude-code, 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…