Harness-neutral engineering toolkit — TS canonical sources for skills, agents, and hooks, with per-harness bundle emit (Claude Code, Codex, OpenCode).
Boundary-first system thinking — contracts over implementations, challenges coupling.
Git conflict resolution — preserves intent from both sides, verifies after resolution.
Outside-in user perspective — progressive disclosure, reduce cognitive load.
Reader-first communication — structural coherence, information architecture, clarity.
Developer-experience advocate — time-to-first-success, guessable APIs, progressive complexity.
Archive lifecycle — condense an xNNN- project to a single archived README; promote important decisions to top-level docs/decisions/; move follow-up to docs/notes/; rewrite cross-references; validate the condensed README; commit atomically. Single-pass variant of the validate-loop. Captain confirms decision promotions per item and the staged README before any source content is deleted.
Capture a locked decision as a numbered dNN-<name>.md file. Use when the captain has answered a load-bearing question that should outlive the conversation, or when lock-decisions / grill-me hands off a captain-locked answer for persistence. Lightweight — no review cycle.
Create a living note — for unresolved decisions, working knowledge, and adapter contracts that don't fit a spike or plan. Use when capturing design context that needs a home but isn't research or a spec.
Plan creation lifecycle — orchestrates project context, per-chapter authoring, and the validate-loop (validate-doc → triage-feedback → revise-doc / process-feedback / lock-decisions) to convergence. Use when the captain asks for a tech spec, implementation plan, or follow-on plan derived from a spike.
Spike lifecycle orchestrator — composes /launch-project, /write-doc, /validate-doc, /triage-feedback, /process-feedback, /revise-doc, and /lock-decisions to drive a full spike from research question to converged chapters with pending clusters surfaced. Use when starting a research spike or resuming one mid-iteration.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
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.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
Lifecycle skills, persona agents, and governance hooks for autonomous-project
workflows — authored once in TypeScript, shipped as native plugin bundles for
Claude Code, Codex, and OpenCode (plus universal skills install via
vercel-labs/skills).
The repo IS the deliverable: clone (or point a marketplace at the GitHub URL) and any of four install verbs picks up the right bundle.
| Component | Count | Examples |
|---|---|---|
| Skills | 21 | create-spike, create-plan, execute-plan, validate-doc, triage-feedback, process-feedback, lock-decisions, start-session, yolo-project, … |
| Persona agents | 11 | architect, qa, dx, reviewer, security, implementer, designer, researcher, verifier, doc-writer, conflict-resolver |
| Governance hooks | 5 | block-main-edits (refuse git commit on main/master), pre-commit-gate (run pnpm run check), pre-write-doc (require yolo new scaffolding for new docs), pre-bash-doc (verify doc-link integrity), verify-worktree-path (refuse edits outside the worktree) |
| CLI scripts | 2 | yolo new <kind> <args> (project/spike/plan/chapter/review/note/decision scaffolder), doc-check-links.sh (cross-reference checker) |
The skill / agent / hook inventory is canonical at
generator/canonical-sources/. Each harness emit ships the same content in
its native layout.
Pick your harness. The first three install verbs all read this repo; the
OpenCode npm path resolves the same content via package.json#main.
claude plugin marketplace add github:mikestopcontinues/agent-skills
claude plugin install agent-skills@agent-skills-dev
That's it. Skills appear as @mikestopcontinues/agent-skills:<skill-name>,
the 11 personas register as dispatchable subagent types, and the 5 hooks
fire automatically on matching tool events (no per-hook trust step — CC
treats plugin-bundled hooks as managed).
# 1. Add the marketplace and enable the plugin
codex plugin marketplace add mikestopcontinues/agent-skills
# Then either toggle on inside the TUI (/plugins → Agent Skills → Install)
# or add to ~/.codex/config.toml manually:
# [plugins."agent-skills@agent-skills-dev"]
# enabled = true
# 2. Enable the plugin_hooks feature flag
# Required for any plugin-bundled hooks to be discovered (Codex ≤0.130 keeps
# this behind a flag). The 21 skills work without it; the 5 hooks do not.
codex features enable plugin_hooks
# 3. Trust the 5 plugin hooks (one-time, interactive)
# Open the TUI: /plugins → Agent Skills → Hooks
# Toggle each hook (block-main-edits, pre-bash-doc, pre-commit-gate,
# pre-write-doc, verify-worktree-path) to Trusted. Codex writes
# [hooks.state."agent-skills@agent-skills-dev:hooks.json:..."] trusted_hash
# entries to ~/.codex/config.toml. Hooks fire on subsequent `codex exec` /
# `codex` sessions.
codex
Skills appear as agent-skills:<skill-name>. The persona agents ship as TOML
files under codex/agents/ and are loaded by the same plugin install.
# Per-project (installs to ./.agents/skills/<name>/)
npx skills add mikestopcontinues/agent-skills
# User-wide (installs to ~/.agents/skills/<name>/)
npx skills add -g mikestopcontinues/agent-skills
Works for [47 agent products][vercel-labs/skills] including Claude Code,
Codex, OpenCode, Cursor, Gemini CLI, Warp, GitHub Copilot. Installs the
skills only — no persona agents, no hooks, no scripts — because the
universal .agents/skills/<name>/SKILL.md convention is the only thing all
47 agents agree on. For full hook / agent coverage on a specific harness,
use that harness's native install path above.
OpenCode has two install paths because its plugin and skill systems are separate concerns:
# Skills (via the universal route)
npx skills add mikestopcontinues/agent-skills
# Hooks (via npm + opencode.json)
npm install @mikestopcontinues/agent-skills@github:mikestopcontinues/agent-skills
Then in opencode.json:
{
"plugin": ["@mikestopcontinues/agent-skills"]
}
The npm package's package.json#main points at ./opencode/src/plugin.ts
which OpenCode loads to register the 5 hooks via the tool.execute.before
plugin API. Skills come from the .agents/skills/ install path that
OpenCode reads natively.
npx claudepluginhub mikestopcontinues/agent-skills --plugin agent-skillsUltra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Memory compression system for Claude Code - persist context across sessions