Instructions file CodexOpenCode
Instructions for escoffier-labs/brigade, covering agents.md, definition of done, rules, orientation and memory handoff.
71 yesterday A 1,962 tokens
original MIT
bug-hunt
02Skill Claude CodeCodex
Use when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
71 yesterday A 45 tokens
original MIT
check
03Skill Claude CodeCodex
Use when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
71 yesterday A 69 tokens
original MIT
Skill Claude CodeCodex
Use when reviewing a diff or module for hidden assumptions - things the code takes for granted that nothing guarantees - or when asked "what could break this later", "what does this assume", or to harden code that works today. Complements bug-hunt: bug-hunt finds defects with triggers today; this finds the ones…
71 yesterday A 73 tokens
original MIT
reduce
05Skill Claude CodeCodex
Use when asked to simplify, clean up, tidy, or refactor code for clarity without changing what it does, or when the user says "simplify this", "clean this up", "make it readable", "reduce the complexity", or "tidy this". Behavior-preserving only; not a bug or security audit (use bug-hunt or security-sweep for those).
71 yesterday A 79 tokens
original MIT
refire
06Skill Claude CodeCodex
Use when anything misbehaves - a failing test, a production bug, a build break, flaky or unexpected behavior - before proposing or attempting any fix. Especially under pressure ("CI is blocking everyone", "just get it green") and after a previous fix didn't hold.
71 yesterday A 57 tokens
original MIT
retry-safety
07Skill Claude CodeCodex
Use when a diff carries side effects - database writes, migrations, file mutations, network calls, payments, queue messages - to check whether running it twice is safe. Also when reviewing retry logic, crash recovery, or anything a scheduler, queue, or impatient caller might re-run. Silent when the diff touches no…
71 yesterday A 71 tokens
original MIT
taste
08Skill Claude CodeCodex
Use when implementing any feature, bugfix, or behavior change, before writing the implementation code. Especially use under pressure - production is down, "just make it work", "quick fix" - which is when it gets skipped.
71 yesterday A 48 tokens
original MIT
brigade-work
09Skill Claude CodeCodex
Use at the start of any work session and whenever you verify a change in a Brigade-wired repo or workspace - routes work through Brigade so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade…
71 yesterday A 85 tokens
original MIT
card-refresh
10Skill Claude CodeCodex
Use when refreshing stale Brigade memory cards from the care refresh queue - category allowlist, grounded edits that cite on-disk sources of truth, archive-only retention, and reinforce-in-place instead of near-duplicate siblings (#724). Never delete, remove, or prune.
71 yesterday A 56 tokens
original MIT
forward-plan
11Skill Claude CodeCodex
Use when turning Brigade's native ready set, outcome rank, and ROADMAP.md into a dependency-filed plan artifact under .brigade/work/plans/ - propose GraphTrail-derived edges (blocks from def/use, conflicts-with from write overlap) marked derived and requiring confirmation. Degrade cleanly when GraphTrail is…
71 yesterday A 73 tokens
original MIT
Skill Claude CodeCodex
Use when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.
71 yesterday A 64 tokens
original MIT
note
13Skill Claude CodeCodex
Create an Obsidian-formatted markdown note documenting the current session topic. Use when the user says /note, 'save this to Obsidian', 'write a note about X', or asks to document a troubleshooting session, system concept, coding pattern, or workflow. Writes to /notes/ .md and syncs to the configured Obsidian inbox.…
71 yesterday A 96 tokens
original MIT
Skill Claude CodeCodex
Use when the user asks for ultra work, scout work, broad pre-implementation scouting, or parallel investigation before a large Brigade task. Designed for Codex and other SKILL.md harnesses that can delegate or split work.
71 yesterday A 51 tokens
original MIT
skillet
15Plugin Claude Code
A skillet full of agent skills for repo audits, publish gates, execution discipline, memory handoffs, and decision-ready briefs.
4 7d ago A
tokens not measured
original MIT
skillet
16Plugin Claude Code
Production-tested skills for auditing, improving, shipping, and preserving repo memory with AI coding agents.
4 7d ago A
tokens not measured
original MIT
SessionStart
17Hook
Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From escoffier-labs/skillet.
4 7d ago A
tokens not measured
copy · 86% MIT
brief
18Skill Claude CodeCodex
Use when answering at a decision point - recommending an approach, reporting a verification result, finishing a task, proposing a fix, or assessing whether something is ready - so the judgment leads and the reader can evaluate it instead of only accepting it. Triggers on "brief mode", "bluf this", "give me the bottom…
4 7d ago C 80 tokens
original MIT
Skill Claude CodeCodex
Use when setting up, checking, writing, linting, or troubleshooting Brigade memory handoffs for a repo or agent workspace, especially when a user wants durable agent memory, handoff inboxes, cross-harness memory routing, or a safe first Brigade setup.
4 7d ago A 58 tokens
original MIT
bug-hunt
20Skill Claude CodeCodex
Use when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
4 7d ago A 45 tokens
copy · 94% MIT
check
21Skill Claude CodeCodex
Use when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
4 7d ago A 69 tokens
copy · 92% MIT
demi
22Skill Claude CodeCodex
Use before implementing, scaffolding, prototyping, or adding a feature when the work should start with the smallest useful code path, avoid speculative architecture, or prevent overbuilding before reduce would be needed.
4 7d ago A 43 tokens
original MIT
expedite
23Skill Claude CodeCodex
Use when the user wants to act on an audit, fix the findings in a line-check/bug-hunt/security-sweep/latent-premises/retry-safety report, work a prioritized backlog, or asks to "fix the findings", "work the backlog", "clear the audit", or "do the high-leverage items". The step after the audit roster.
4 7d ago A 78 tokens
original MIT
fire
24Skill Claude CodeCodex
Use when a written implementation plan is ready to execute, when the user says "fire", "execute the plan", "build it", or hands over a plan file to implement. The step after recipe.
4 7d ago A 43 tokens
original MIT