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 sealgit 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/seal)<a href="https://agentmods.dev/skills/alexander-tyagunov/magician/seal"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/seal/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/seal"><img src="https://agentmods.dev/badge/skills/alexander-tyagunov/magician/seal.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.00035 | $0.01742 |
| Opus 5.5 | $0.00014 | $0.00697 |
| Sonnet 5.5 | $0.00007 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
seal 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/seal — Ship to Production
Take a certified feature branch through to a merged PR. This skill performs irreversible actions (push, PR, merge) — it presents a single consolidated ship-summary and waits before the first outward command (git push).
Pre-flight
- Confirm /certify has been run and passed
- Confirm the /scrutinize review + remediation cycle is complete (or explicitly skipped by user)
- Never ship on stale evidence — /certify must have passed in this session (fresh output you read this turn), not a remembered run. See lore/verification.md.
Autonomy — approve the plan, then run
Once Pre-flight is confirmed (/certify passed, /scrutinize + remediation complete or explicitly skipped), the ship sequence runs autonomously: the Simplifier Pass, Final Certify, Update Documentation, and Commit steps proceed without stopping to ask the owner. Claude Code's built-in read-only commands (including read-only git) don't prompt; this skill pre-approves the exact commit, push, PR, CI-check and merge commands shown below and edits to CLAUDE.md/README.md; any other edit or command goes through the normal permission prompt unless the user runs in auto mode. Re-gate only on outward side effects — git push, gh pr create, gh pr merge — surfaced once through the consolidated ship-summary gate below, not per command. Doctrine: lore/autonomy.md.
Process
1. Simplifier Pass
Dispatch the simplifier via Task with subagent type magician:simplifier for a final simplification sweep. Give it a self-contained prompt: the goal, the changed files (with diff), and the return format (see lore/subagent-context.md). Fix any Important findings. Skip Low suggestions unless trivial.
2. Final Certify
Run /certify. All checks must pass before continuing — including style vs the project's documented conventions (lore/code-standards.md), so review bounces on style don't reopen the ship loop.
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 · +110 lines 9c99ed38f1dd
- 1mo ago First seen · 17 lines · 35 tokens per session scan A 6afa7c1045e9
seal is a skill published in the GitHub repository Alexander-Tyagunov/magician (14 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 1,742 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.