everything-claude-code-harness
Agent harness performance system for Claude Code and other AI coding agents — skills, instincts, memory, hooks, commands, and security scanning
What this skill does
# Everything Claude Code (ECC) — Agent Harness Performance System
> Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection.
Everything Claude Code (ECC) is a production-ready performance optimization system for AI agent harnesses. It provides specialized subagents, reusable skills, custom slash commands, memory-persisting hooks, security scanning, and language-specific rules — all evolved from 10+ months of daily real-world use. Works across Claude Code, Cursor, Codex, OpenCode, and Antigravity.
---
## Installation
### Option 1: Plugin Marketplace (Recommended)
```bash
# Inside Claude Code, run:
/plugin marketplace add affaan-m/everything-claude-code
/plugin install everything-claude-code@everything-claude-code
```
### Option 2: Manual Clone
```bash
git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code
# Install rules for your language stack
./install.sh typescript
# Multiple languages:
./install.sh typescript python golang swift
# Target a specific IDE:
./install.sh --target cursor typescript
```
### Install Rules (Always Required)
Claude Code plugins cannot auto-distribute rules — install them manually via `./install.sh` or copy from `rules/` into your project's `.claude/rules/` directory.
---
## Directory Structure
```
everything-claude-code/
├── .claude-plugin/ # Plugin and marketplace manifests
│ ├── plugin.json
│ └── marketplace.json
├── agents/ # Specialized subagents (planner, architect, etc.)
├── commands/ # Slash commands (/plan, /security-scan, etc.)
├── skills/ # Reusable skill modules
├── hooks/ # Lifecycle hooks (SessionStart, Stop, PostEdit, etc.)
├── rules/
│ ├── common/ # Language-agnostic rules
│ ├── typescript/
│ ├── python/
│ ├── golang/
│ └── swift/
├── scripts/ # Setup and utility scripts
└── install.sh # Interactive installer
```
---
## Key Commands
After installation, use the namespaced form (plugin install) or short form (manual install):
```bash
# Planning & architecture
/everything-claude-code:plan "Add OAuth2 login flow"
/everything-claude-code:architect "Design a multi-tenant SaaS system"
# Research-first development
/everything-claude-code:research "Best approach for rate limiting in Node.js"
# Security
/everything-claude-code:security-scan
/everything-claude-code:harness-audit
# Agent loops and orchestration
/everything-claude-code:loop-start
/everything-claude-code:loop-status
/everything-claude-code:quality-gate
/everything-claude-code:model-route
# Multi-agent workflows
/everything-claude-code:multi-plan
/everything-claude-code:multi-execute
/everything-claude-code:multi-backend
/everything-claude-code:multi-frontend
# Session and memory
/everything-claude-code:sessions
/everything-claude-code:instinct-import
# PM2 orchestration
/everything-claude-code:pm2
# Package manager setup
/everything-claude-code:setup-pm
```
> With manual install, drop the `everything-claude-code:` prefix: `/plan`, `/sessions`, etc.
---
## Hook Runtime Controls
ECC hooks fire at agent lifecycle events. Control strictness at runtime without editing files:
```bash
# Set hook strictness profile
export ECC_HOOK_PROFILE=minimal # Least intrusive
export ECC_HOOK_PROFILE=standard # Default
export ECC_HOOK_PROFILE=strict # Maximum enforcement
# Disable specific hooks by ID (comma-separated)
export ECC_DISABLED_HOOKS="pre:bash:tmux-reminder,post:edit:typecheck"
```
Hook events covered: `SessionStart`, `Stop`, `PostEdit`, `PreBash`, `PostBash`, and more.
---
## Package Manager Detection
ECC auto-detects your package manager with this priority chain:
1. `CLAUDE_PACKAGE_MANAGER` environment variable
2. `.claude/package-manager.json` (project-level)
3. `package.json` → `packageManager` field
4. Lock file detection (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `bun.lockb`)
5. `~/.claude/package-manager.json` (global)
6. First available manager as fallback
```bash
# Set via environment
export CLAUDE_PACKAGE_MANAGER=pnpm
# Set globally
node scripts/setup-package-manager.js --global pnpm
# Set per-project
node scripts/setup-package-manager.js --project bun
# Detect current setting
node scripts/setup-package-manager.js --detect
```
---
## Skills System
Skills are markdown modules the agent loads to gain domain expertise. Install individually or in bulk.
### Using a Skill
```bash
# Reference a skill explicitly in your prompt
"Use the search-first skill to find the right caching approach before implementing"
# Or trigger via slash command
/everything-claude-code:research "content hashing strategies for API responses"
```
### Notable Built-in Skills
| Skill | Purpose |
|---|---|
| `search-first` | Research before coding — avoids hallucinated APIs |
| `cost-aware-llm-pipeline` | Optimizes token spend across model calls |
| `content-hash-cache-pattern` | Cache invalidation via content hashing |
| `skill-stocktake` | Audits which skills are loaded and active |
| `frontend-slides` | Zero-dependency HTML presentation builder |
| `configure-ecc` | Guided interactive ECC setup wizard |
| `swift-actor-persistence` | Swift concurrency + persistence patterns |
| `regex-vs-llm-structured-text` | Decides when to use regex vs LLM parsing |
### Writing a Custom Skill
Create `skills/my-skill.md`:
```markdown
---
name: my-skill
description: What this skill does
triggers:
- "phrase that activates this skill"
---
# My Skill
## When to Use
...
## Pattern
\`\`\`typescript
// concrete example
\`\`\`
## Rules
- Rule one
- Rule two
```
---
## Instincts System (Continuous Learning)
Instincts are session-extracted patterns saved for reuse. They carry confidence scores and evolve over time.
### Export an Instinct
```bash
/everything-claude-code:instinct-import
```
### Instinct File Format
```markdown
---
name: prefer-zod-for-validation
confidence: 0.92
extracted_from: session-2026-02-14
---
# Action
Always use Zod for runtime schema validation in TypeScript projects.
# Evidence
Caught 3 runtime type errors that TypeScript alone missed during session.
# Examples
\`\`\`typescript
import { z } from 'zod'
const UserSchema = z.object({
id: z.string().uuid(),
email: z.string().email(),
role: z.enum(['admin', 'user'])
})
type User = z.infer<typeof UserSchema>
\`\`\`
```
---
## Rules Architecture
Rules enforce coding standards per language. Install only what your stack needs.
```bash
# TypeScript + Python
./install.sh typescript python
# Check what's installed
ls .claude/rules/
```
### Rule Directory Layout
```
rules/
├── common/ # Applies to all languages
│ ├── research-first.md
│ ├── security-baseline.md
│ └── verification-loops.md
├── typescript/
│ ├── no-any.md
│ ├── zod-validation.md
│ └── strict-mode.md
├── python/
│ ├── type-hints.md
│ └── django-patterns.md
└── golang/
└── error-wrapping.md
```
---
## Agents (Subagent Delegation)
Agents are specialized personas the orchestrator delegates to:
```bash
# In your prompt, reference an agent explicitly
"Delegate architecture decisions to the architect agent"
"Use the planner agent to break this feature into tasks"
```
Available agents include: `planner`, `architect`, `researcher`, `verifier`, `security-auditor`, and more. Each lives in `agents/<name>.md` with its own system prompt, tools list, and constraints.
---
## AgentShield Security Scanning
Run security scans directly from Claude Code:
```bash
/everything-claude-code:security-scan
```
This invokes the AgentShield scanner (1282 tests, 102 rules) against your codebase and surfaces:
- Hardcoded secrets
- Injection vulnerabilities
- Insecure dependencies
- Agent prompt injection patterns
---
## Memory Persistence Hooks
ECC hooks automatically save and restore session context:
```javascript
// hooks/session-start.js — loads prior context on new session
const fs = require('fs')
const pRelated in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.