Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add aaronnat23/disp8ch --skill crew-lifecyclegit clone --depth 1 https://github.com/aaronnat23/disp8chWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aaronnat23/disp8ch/crew-lifecycle)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/crew-lifecycle"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/crew-lifecycle.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00255 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
crew-lifecycle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Crew Lifecycle
Use this skill when coordinating a live crew across hierarchy, approvals, and boards.
Lifecycle states:
planning: define scope, create the plan task, request approvalready: approval granted, dependencies created, wakeups queuedexecuting: specialists are working and blocked tasks are trackedwaiting: crew is paused on approval, blockers, or missing inputclosing: synthesis, handoff, and cleanup
Operating pattern:
- Keep one board task for the mission and separate child tasks for the active work lanes.
- Use
blocked_byso synthesis or rollout tasks do not start too early. - Use
governance_queue enqueue-wakeupwhen a teammate should resume work. - Use
agent_inboxto broadcast mission changes or decisions to the crew. - Check
governance_queue agent-runtimewhen a member appears stalled or failed.
What to report:
- Pending approvals
- Blocked tasks
- Queued wakeups
- Members with unread inbox items
- Last failed agent or workflow
Avoid:
- Starting execution without a plan or approval when one is required
- Leaving blocked tasks without visible blockers
- Spamming wakeups without changing the task state or message context
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 30 lines · 0 tokens per session scan A 414782dfd880
crew-lifecycle is a skill published in the GitHub repository aaronnat23/disp8ch (99 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 255 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
agentlas-operations
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.
todo-tracker
Persistent TODO scratch pad for tracking tasks across sessions. Use when the user asks to add, list, complete, remove, or summarize tasks in a portable workspace Markdown file. Uses stable task IDs and exact matching; heartbeat reporting is opt-in and count-only.
prd
A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.
linear
Manage Linear teams, projects, cycles, issues, comments, workflow state, and documents from a terminal through Linear's public GraphQL API. Use when a user asks to list, search, inspect, create, update, move, or comment on Linear work, or to find Linear documents. Do not use to embed a live agent inside Linear or to…
planner
Interactive planning and execution for complex tasks. Use when breaking down multi-step projects (planning) or executing approved plans through delegation (execution). Planning creates milestones with specifications; execution delegates to specialized agents. Use when you say "plan this feature", "create…
duduclaw-platform
Use the DuDuClaw MCP tools (persistent memory, shared wiki, task board, channel messaging) when the user asks to remember something across sessions, share knowledge with their team's AI employees, manage tasks, or message someone on LINE/Telegram/Discord/Slack. Requires a running DuDuClaw gateway (npx duduclaw onboard…