claudesec
CLAUDE.md16 starsChanged 6 months agoMITView on GitHub
You are running with oh-my-claudecode (OMC), a multi-agent orchestration layer for Claude Code. Coordinate specialized agents, tools, and skills so work is completed accurately and efficiently. Say "setup omc" or run /oh-my-claudecode:omc-setup.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- scanner/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/claude-agents-and-practices.mdcCursor rule
- .cursor/rules/claudesec-project.mdcCursor rule
- .cursor/rules/markdown-quality.mdcCursor rule
- .cursor/rules/no-sensitive-paths.mdcCursor rule
- .cursor/rules/security-citations.mdcCursor rule
- ci-config-guard-claudesecSkill
- kcov-debugSkill
- lychee-redirect-triageSkill
- omc-referenceSkill
The file
We split this CLAUDE.md into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Prefer evidence over assumptions: verify outcomes before final claims.
- Distinctive: line 36
Verify before claiming completion.
- Distinctive: line 37
If verification fails, keep iterating.
- Very specific: line 42
Keep authoring and review as separate passes: writer pass creates or revises content, reviewer/verifier pass evaluates it later in a …
- Very specific: line 43
Never self-approve in the same active context.
- Distinctive: line 44
Before concluding: zero pending tasks, tests passing, verifier evidence collected.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- OMC:START --><!-- OMC:VERSION:4.11.0 -->oh-my-claudecode - Intelligent Multi-Agent Orchestration
You are running with oh-my-claudecode (OMC), a multi-agent orchestration layer for Claude Code. Coordinate specialized agents, tools, and skills so work is completed accurately and efficiently.
<operating_principles>
- Delegate specialized work to the most appropriate agent.
- Prefer evidence over assumptions: verify outcomes before final claims.
- Choose the lightest-weight path that preserves quality.
- Consult official docs before implementing with SDKs/frameworks/APIs. </operating_principles>
<delegation_rules>
Delegate for: multi-file changes, refactors, debugging, reviews, planning, research, verification.
Work directly for: trivial ops, small clarifications, single commands.
Route code to executor (use model=opus for complex work). Uncertain SDK usage → document-specialist (repo docs first; Context Hub / chub when available, graceful web fallback otherwise).
</delegation_rules>
<model_routing>
haiku (quick lookups), sonnet (standard), opus (architecture, deep analysis).
Direct writes OK for: ~/.claude/**, .omc/**, .claude/**, CLAUDE.md, AGENTS.md.
</model_routing>
<skills>
Invoke via `/oh-my-claudecode:<name>`. Trigger patterns auto-detect keywords.
Tier-0 workflows include `autopilot`, `ultrawork`, `ralph`, `team`, and `ralplan`.
Keyword triggers: `"autopilot"→autopilot`, `"ralph"→ralph`, `"ulw"→ultrawork`, `"ccg"→ccg`, `"ralplan"→ralplan`, `"deep interview"→deep-interview`, `"deslop"`/`"anti-slop"`→ai-slop-cleaner, `"deep-analyze"`→analysis mode, `"tdd"`→TDD mode, `"deepsearch"`→codebase search, `"ultrathink"`→deep reasoning, `"cancelomc"`→cancel.
Team orchestration is explicit via `/team`.
Detailed agent catalog, tools, team pipeline, commit protocol, and full skills registry live in the native `omc-reference` skill when skills are available, including reference for `explore`, `planner`, `architect`, `executor`, `designer`, and `writer`; this file remains sufficient without skill support.
</skills><verification>
Verify before claiming completion. Size appropriately: small→haiku, standard→sonnet, large/security→opus.
If verification fails, keep iterating.
</verification><execution_protocols>
Broad requests: explore first, then plan. 2+ independent tasks in parallel. run_in_background for builds/tests.
Keep authoring and review as separate passes: writer pass creates or revises content, reviewer/verifier pass evaluates it later in a separate lane.
Never self-approve in the same active context; use code-reviewer or verifier for the approval pass.
Before concluding: zero pending tasks, tests passing, verifier evidence collected.
</execution_protocols>
<hooks_and_context>
Hooks inject <system-reminder> tags. Key patterns: hook success: Success (proceed), [MAGIC KEYWORD: ...] (invoke skill), The boulder never stops (ralph/ultrawork active).
Persistence: <remember> (7 days), <remember priority> (permanent).
Kill switches: DISABLE_OMC, OMC_SKIP_HOOKS (comma-separated).
</hooks_and_context>
<cancellation>
`/oh-my-claudecode:cancel` ends execution modes. Cancel when done+verified or blocked. Don't cancel if work incomplete.
</cancellation><worktree_paths>
State: .omc/state/, .omc/state/sessions/{sessionId}/, .omc/notepad.md, .omc/project-memory.json, .omc/plans/, .omc/research/, .omc/logs/
</worktree_paths>
Setup
Say "setup omc" or run /oh-my-claudecode:omc-setup.
<!-- OMC:END -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

