everything-claude-code-harness — Claude Code skill: agents, hooks
The skill builds out an agent harness: subagents, slash commands, memory hooks and a security scan. Useful when every Claude session starts from a blank slate.
npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a claude-codeWhat everything-claude-code-harness does
Inside the skill you get a set of specialised subagents, skill modules, custom slash commands, lifecycle hooks and language rules. Commands run with the plugin prefix, so a planning call looks like /everything-claude-code:plan and a scan like /everything-claude-code:security-scan.
Hooks listen on SessionStart, Stop, PostEdit, PreBash and PostBash. Strictness comes from ECC_HOOK_PROFILE — minimal, standard or strict — and individual hooks are switched off by listing them in ECC_DISABLED_HOOKS. Package manager detection walks a chain that starts with CLAUDE_PACKAGE_MANAGER, then .claude/package-manager.json, then lock files.
The rules/ folder is not shipped into your project by the plugin. You copy the stack you need into .claude/rules/ or call ./install.sh with a stack name such as ./install.sh typescript, adding --target cursor when the rules should land in Cursor. Skip that step and the agent picks up commands and hooks while the rules never arrive.
What it helps with
- put the right rules for a TypeScript, Python, Go or Swift repo in place
- run a security scan before pushing a branch
- turn a pattern from a past session into a reusable instinct
- switch hook strictness to match the task at hand
- plan multi-agent work that spans backend and frontend
Example prompts for the agent
- Run
/everything-claude-code:plan "Add an OAuth2 login flow"and lay out the steps - Scan the current branch with
/everything-claude-code:security-scan - Look into caching options first:
/everything-claude-code:research "content hashing for API responses"
How to install everything-claude-code-harness
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a claude-code2Manually: put the files in place
~/.claude/skills/everything-claude-code-harness/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/everything-claude-code-harness/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a codex2Manually: put the files in place
.agents/skills/everything-claude-code-harness/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a cursor2Manually: put the files in place
.cursor/skills/everything-claude-code-harness/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/trending-skills everything-claude-code-harness2Manually: put the files in place
.github/skills/everything-claude-code-harness/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/trending-skills --path skills/everything-claude-code-harnessManually: put the files in place
.devin/skills/everything-claude-code-harness/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about everything-claude-code-harness
How do I install everything-claude-code-harness in Claude Code?
Run npx skills add reason-machines/trending-skills --skill everything-claude-code-harness -a claude-code. The skill lands at ~/.claude/skills/everything-claude-code-harness/SKILL.md.
What does everything-claude-code-harness do?
It gives the agent a working harness: subagents, skills, slash commands, hooks that persist memory across sessions, and rules for the project's language stack.
Why are no rules active after install?
Claude plugins can't push rules into a project by themselves. Copy the folders you need from rules/ into .claude/rules/, or run ./install.sh with a stack name.