Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
Use to orient in an unfamiliar codebase with graphify, a local tree-sitter code graph — "what does this symbol touch", "how do these two connect", "trace this call chain". Opt-in (the human installs graphify once). A forward-orientation aid, NOT a reliable reverse-dependency tool. Shipped and kept current by Loom.
Revenue infrastructure for autonomous AI agents on Base. Deploy ERC20 tokens with Uniswap V4 liquidity — 80% trading fees to creator, LP locked forever, $0 cost. 148 tokens live. Own contracts (no Clanker dependency). Direct blockchain calls = zero downtime. CLI, MCP server, or smart contract.
Install structured self-improvement loops with instinct-based learning into Claude Code — research, plan, execute, verify, reflect, learn, iterate. On-demand or weekly analysis to save tokens. Supports multi-agent parallel analysis.
Orchestre une tâche complexe en trois temps avec Claude Code — PLANIFIER avec le modèle le plus puissant (Fable 5 / Opus), DÉLÉGUER l'exécution à des sous-agents calibrés lot par lot (Haiku / Sonnet / Opus selon la complexité) lancés en parallèle, puis VÉRIFIER chaque livrable de façon adversariale avec le modèle…
Create a detailed implementation plan before coding. Use when starting a new feature, multi-step refactor, or complex task. Invoked by saying "plan", "create a plan", or "plan this task".
The Filter (兔). Orchestrator and post-processor that makes LLM output actually readable. Invokes other zodiac animals based on what the user needs, then synthesizes and reshapes their raw output for the specific human reading it. Breaks the LLM default of audience-blind verbosity — walls of text, wrong detail level…
Use when auditing, pruning, or cleaning up an agent's entire existing rule set in one bulk pass across every rule source at once (all CLAUDE.md files, all memory entries, AGENTS.md, ADRs, COORDINATION). This is whole-corpus hygiene; NOT for adding, editing, or fixing an individual rule (just edit that file directly).
Route token-heavy context, noisy shell logs and output through the smallest measured CLI or projection before loading heavy tools; recall past agent sessions before re-deriving; fan out to free lanes; benchmark cheap subagent workflows without broad prompt bloat.
Use only when the user explicitly asks to start, operate, inspect, shutdown, or restart a Team Agent team. Treat the team-agent CLI as a sealed appliance.
Plan and supervise user-approved software initiatives through Codex native tasks and bounded native subagents. Use when the user explicitly asks Agent Orchestration Gateway to clarify work, split it into non-overlapping modules, dispatch module tasks, or run an AOG module task.
Spawn Claude Opus 5 or Fable 5 as an external subagent through the Claude Code CLI, supervised by exactly one GPT-5.6 Sol low-effort babysitter. Use automatically when the user says "spawn Opus 5", "spawn Fable 5", asks for an Opus 5 or Fable 5 sub-agent, or asks Codex to delegate a task to either Claude model.
DEPRECATED — Use /enterprise instead. This skill has been superseded by the modular enterprise pipeline (/enterprise orchestrator + /enterprise-discover, /enterprise-brainstorm, /enterprise-plan, /enterprise-contract, /enterprise-build, /enterprise-review, /enterprise-forge, /enterprise-verify, /enterprise-compound).…
Use when the user is running one or more coding agents and needs a shared control plane to coordinate work and keep an audit trail. Triggers include running parallel Claude Code/Cursor sessions, agents colliding on the same work, needing objectives instead of a task list, or needing auditable evidence of…
Use when the user wants to create, add, extend, or modify an agent, skill, or workflow in this kit (e.g. "create a skill for our dbt naming standard", "add an agent for X", "new workflow"). Decides whether to build an agent, a skill, or nothing, enforces lean quality standards, and keeps every installed AI-tool folder…
Non-custodial Lightning wallet for AI agents via sz CLI: send/receive sats, pay invoices, auto-pay HTTP 402 (L402), manage channels and liquidity. Use when: (1) paying for API access with Lightning, (2) creating or paying BOLT11 invoices, (3) checking wallet balance or channel health, (4) managing peers and channels.…
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Set up state-of-the-art context engineering for any repository. Analyzes codebase, generates multi-level CLAUDE.md/AGENTS.md hierarchy, hooks, session management, and token budgets. Based on 200+ sources including ETH Zurich, Anthropic, Google DeepMind, and Manus production data. For engineers who ship with AI agents.
Wire mnemostack into OpenClaw as an MCP server, alongside the native OpenClaw memory tools (memorysearch / memoryget). The two coexist — mnemostack handles the hybrid pipeline (Vector + BM25 + Memgraph + Temporal + 8-stage rerank), while the native tools do fast file-scoped retrieval.
Deploy and extend small web artifacts ("canvases") on a canvas-drop instance. Use when the user wants to ship static HTML/JS to a shared URL, or give a canvas backend capability (KV, files, AI, identity, realtime, admin-granted Connections) through the zero-config browser SDK. Connect over MCP for an identity-scoped…
Use Infinity Context MCP to search, propose, and manage durable project memory.
★not rated 7 todayA17 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: