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 Alexander-Tyagunov/magician --skill manifestgit clone --depth 1 https://github.com/Alexander-Tyagunov/magicianWrote 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/alexander-tyagunov/magician/manifest)<a href="https://agentmods.dev/skills/alexander-tyagunov/magician/manifest"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/manifest/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alexander-tyagunov/magician/manifest"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/manifest.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01744 |
| Opus 5.5 | $0.00009 | $0.00698 |
| Sonnet 5.5 | $0.00005 | $0.00349 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
manifest 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/manifest — Full Autonomous SDLC
The complete end-to-end development flow. Four human gates. Everything else runs autonomously.
Autonomy is the point: gather → plan → memorize → execute. The human approves the gates below, not each file read. Ground via kg (not broad grep), memorize the plan + requirements + kg pointers + standards to .workspace/, and execute the whole plan without stopping to ask about individual reads/searches — Claude Code's built-in read-only commands never prompt, and anything else prompts once unless the user runs in auto mode or approves it. The gates you stop on are writes/commit/push/PR/ticket/destructive ops. If you're bombarding the owner with "can I read this?" the run is broken. See lore/autonomy.md.
/manifest is the greenfield entry (build something new). For brownfield work — recreate an existing feature in another app, or change one in place (swap the vendor behind the scenes, redesign, add a capability) — use /transmute, which comprehends the existing feature first and then drives the same delivery spine (conjure → blueprint → weave → gateways → seal) behind a parity contract.
A full SDLC run is large — prefer the latest model and a high reasoning effort (/effort high; for big features, your model's deepest level — xhigh, or max on models that lack it). If the session is on an older model, suggest upgrading before starting. See lore/models.md.
Gates (Human Approval Required)
GATE 1: Scope approval
GATE 2: Spec approval (after /conjure)
GATE 3: Plan approval (after /blueprint)
GATE 4: PR title and final go-ahead (before /seal)
Process
Phase 0: Scope Triage [GATE 1]
- Ask: "What do you want to build?" (one sentence description). End your turn. Wait for their answer before assessing anything.
- Assess scope — is this one coherent feature or multiple independent subsystems?
- If too large: help decompose into sub-features, each with its own /manifest cycle
- Present scope to user, then gate with AskUserQuestion — options: Approve (proceed to Phase 1), Revise scope (adjust the boundaries first), Split into sub-features (too big — decompose into separate /manifest cycles). End your turn at the call; wait for the choice. Treat a free-form "yes / approved / looks good" as Approve; proceed to Phase 1 only on Approve.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +76 lines ddcf0519bead
- 1mo ago First seen · 11 lines · 23 tokens per session scan A 103e3b04b416
manifest is a skill published in the GitHub repository Alexander-Tyagunov/magician (14 stars, last pushed 29d ago), licensed MIT. It adds 23 tokens to every session and 1,744 once invoked, about $0.0001 per session on Opus 5.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
gh-monitor-pr
Start a detached GitHub pull-request monitor that wakes the exact launching Codex Desktop or CLI root through the managed Codex App Server when review, CI, conflict, merge-queue, closure, readiness, or merge events need attention. Use when the user asks Codex to watch, monitor, babysit, or wait on a PR or merge queue…
dev-git-workflow
Designs team Git workflows for branching, PRs, and releases. Use when choosing branching models, stacked PRs, merge queues, worktree isolation for agents, or collaboration rules.
changelog
Generate or update CHANGELOG.md with an entry for the unreleased changes since the last git tag. Invoke when the user asks to cut a release, update the changelog, or summarize changes since v-something.
doc-changelog
CHANGELOG maintenance following Keep a Changelog. Trigger when the user wants to document changes or prepare a release.
ship-task
Use to wrap up a finished task - set status to done, merge, clean up.
id-rollback
The infra-delivery INCIDENT safe-revert PROCEDURE skill (the recurring/incident rollback step) — the PROCEDURE the generic agent runs when a delivered change did NOT land (a NOT-LANDED realization, an escaped defect, bad config) to restore the last-known-good IaC and prove reality matches it again. The shape is git…