By ctoth
Behavioral protocol skills for Claude Code agents — foreman coordination, gauntlet pipeline, investigation debugging, and more. Integrates with ward for mechanical tool restriction enforcement.
Reverse engineering protocol. The work product is documentation. Decompile function, document findings in NOTES.md, then next function. Never batch discoveries, never mark phase complete without reviewing NOTES.md against phase requirements.
Read-only design review against project principles. Checks whether a design or implementation aligns with or violates the project's stated principles. Does not check code quality, bugs, tests, style, or performance — only directional alignment.
Use Codex and Gemini CLIs as external reviewers for gated review chunks. They read prompt files and write reports. Use for pre-implementation review, spec validation, architecture critique, or second opinions.
Coordination-only protocol. You dispatch subagents, you do not execute code. Restricts tools to Read, Write (prompts/ and notes- only), Agent, Glob, Grep. Use when orchestrating multi-agent work.
Four-role sequential pipeline for complex, high-risk changes. Scout surveys the codebase, Coder implements with TDD, Analyst finds problems, Verifier gates the merge. Use for large refactors, architectural shifts, and interdependent multi-phase work.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Agent behavioral protocols for Claude Code, with mechanical tool restriction enforcement via ward.
Provides 11 behavioral protocol skills that define operational modes for Claude Code agents. Each protocol constrains agent behavior — what tools are available, what workflow to follow, what the agent's role is.
Protocols that restrict tools (foreman, adversary, researcher) include ward gate rules that mechanically enforce those restrictions at the PreToolUse hook level, preventing accidental violations.
| Protocol | Description |
|---|---|
| foreman | Coordination only — dispatch subagents, do not execute code |
| subagent | How to write and launch subagent prompts (auto-invocable) |
| gauntlet | Scout -> Coder -> Analyst -> Verifier pipeline for high-risk changes |
| investigation | Structured debugging with competing hypotheses and escalation levels |
| phases | Parallel/sequential workflow phases with filesystem-based coordination |
| iterations | Tracked iteration cycles for reducing failures with regression detection |
| adversary | Read-only design review against project principles |
| researcher | Pre-implementation research with web access |
| external-agents | Using Codex/Gemini CLIs as external reviewers |
| spec-updating | Spec update workflow with discovery, draft, and review gates |
| RE | Reverse engineering — documentation is the work product |
Protocols that restrict tools use ward for mechanical enforcement:
ward-rules/ directory via WARD_RULES_PATHward set foreman), ward's session.phase is set| Rule | Phase | Denies |
|---|---|---|
foreman-gate.yaml | foreman | Bash, Edit, Write (except prompts/ and notes-*) |
adversary-gate.yaml | adversary | Edit, Write, Bash |
researcher-gate.yaml | researcher | Edit (Write allowed for reports) |
claude plugin marketplace add ctoth/protocols-plugin
claude plugin install protocols@protocols-marketplace
WARD_RULES_PATH for loading rules from plugin directoriesActivate a protocol by invoking it as a skill:
/protocols:foreman # Enter foreman coordination mode
/protocols:gauntlet # Start a scout->coder->analyst->verifier pipeline
/protocols:investigation # Begin structured debugging
/protocols:adversary # Run read-only principle alignment check
/protocols:researcher # Enter research mode with web access
The subagent protocol is auto-invocable — it provides background knowledge whenever you dispatch agents.
Protocols that restrict tools will instruct you to run ward set <protocol> to activate mechanical enforcement.
MIT
npx claudepluginhub ctoth/protocols-plugin --plugin protocolsAnnotated research paper collection management — retrieve, read, extract, cross-reference scientific papers
This skill should be used when the model's ROLE_TYPE is orchestrator and needs to delegate tasks to specialist sub-agents. Provides scientific delegation framework ensuring world-building context (WHERE, WHAT, WHY) while preserving agent autonomy in implementation decisions (HOW). Use when planning task delegation, structuring sub-agent prompts, or coordinating multi-agent workflows.
/catalog for protocol handbook, /onboard for quick recommendation + protocol learning, /report for Growth Map (usage analysis + insights integration), /dashboard for coverage dashboard, /compose for protocol composition authoring, /sophia for philosopher match (behavioral dimension analysis), /curses for strength-shadow analysis and attitude recommendations
Structured protocols for feature exploration and development workflows
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Memory compression system for Claude Code - persist context across sessions
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.