Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add corezoid/corezoid-ai-plugin/plugin install corezoidWrote 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/corezoid/corezoid-ai-plugin/corezoid-lifecycle)<a href="https://agentmods.dev/skills/corezoid/corezoid-ai-plugin/corezoid-lifecycle"><img src="https://agentmods.dev/badge/skills/corezoid/corezoid-ai-plugin/corezoid-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.00153 | $0.01045 |
| Opus 5 | $0.00077 | $0.00522 |
| Sonnet 5 | $0.00031 | $0.00209 |
| Haiku 4.5 | $0.00015 | $0.00104 |
Grade A, and why
corezoid-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corezoid Lifecycle and Move Operations
Use this skill for deliberate operational changes to existing Corezoid objects. These tools act on live server state and require explicit user intent.
Read ${CLAUDE_PLUGIN_ROOT}/docs/process/process-lifecycle-and-move.md before
the first lifecycle/move operation in a session.
Non-negotiable authorization rule
Never pause, resume, or move an object automatically.
The following are not authorization:
- a process appears unused;
- a review or refactor is in progress;
- edits/tests have completed;
- a folder layout looks untidy;
- pausing or moving would be a convenient safety precaution.
The user must directly ask for the specific action. If the exact object or destination is ambiguous, resolve candidates read-only and ask the user to choose. Do not infer a target.
Required two-step workflow
For all four tools:
- Resolve and repeat back the exact object ID/title. For moves, also resolve the exact destination ID/path.
- Call the tool with
apply=false(or omitapply). - Present the dry-run, including current state/location, target, operational effects, and the exact confirmation token.
- Ask for explicit confirmation. Do not invent confirmation from earlier general approval. The token is reconstructable and is not itself evidence that the user approved the operation.
- Only after confirmation, call
apply=truewith the exact token returned by the fresh dry-run. - Report the tool's verified result. If it says verification failed or state may already have changed, stop and run a new dry-run; never retry blindly.
Pause a process
Use:
pause-process(process_id=<id>)
pause-process(process_id=<id>, apply=true,
confirm="process#<id>:<live_status>->paused")
Explain before confirmation:
- Corezoid will reject new task creation with
conveyor_is_not_active. - The graph and deployment are unchanged.
- Already-running or parked tasks are not modified by this tool and must be inspected separately.
- Pause is temporary admission control, not evidence that a process is safe to delete.
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.
- 6d ago First seen · 132 lines · 153 tokens per session scan A 1f5dc60092a4
corezoid-lifecycle is a skill published in the GitHub repository corezoid/corezoid-ai-plugin (73 stars, last pushed yesterday), licensed MIT. It adds 153 tokens to every session and 1,045 once invoked, about $0.0008 per session on Opus 5. 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-08-30.
Other skills, from other repositories
stop-that-shit
Keep coding agents focused on requested and necessary work. Use when a request sets a read-only, answer-only, file, action, or stopping boundary; when evidence shows scope creep, speculative hardening, unnecessary hashing or dependencies, repeated audit loops, or valueless delegation; or when the user invokes Stop…
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.
superloopy-loop
Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.
superloopy-clone
Use when the user asks for Superloopy clone or asks to clone, rebuild, reverse-engineer, replicate, or copy a website or page into a Superloopy-governed implementation. Triggers on "loopy clone", target URLs plus requests such as "clone this site", "rebuild this page", "make a copy of this website", "pixel-perfect…
superloopy-doctor
Use when diagnosing Superloopy doctor, install, wrapper, plugin cache, hook bootstrap, bundled agents, marketplace, Codex, Claude Code, stale-version, evidence-floor, or host-wiring health problems.
inspect-codex-trajectory
Inspect or show a local Codex task trajectory, including turns, approximate model steps, assistant messages, reasoning summaries, tool calls, failures, compaction, token usage, and timing. Use when the user asks for a trajectory, execution trace, task timeline, slow-tool analysis, visual event ledger, or live…