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 xbklairith/kisune --skill wizardgit clone --depth 1 https://github.com/xbklairith/kisuneWrote 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/xbklairith/kisune/wizard)<a href="https://agentmods.dev/skills/xbklairith/kisune/wizard"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/wizard/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/xbklairith/kisune/wizard"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/wizard.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.00092 | $0.01192 |
| Opus 5.5 | $0.00037 | $0.00477 |
| Sonnet 5.5 | $0.00018 | $0.00238 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
wizard 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 11d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wizard
Overview
A wizard is a bash script that walks a human through a manual procedure one stage at a time: it opens each URL, says exactly what to click and copy, captures the value, writes it where it belongs (.env, a GitHub secret or variable), confirms before anything irreversible, and shows how many stages are left.
The deliverable is the script. A markdown checklist of the same steps is not a wizard: the human still copies values by hand, mistypes a secret name, and pastes keys into a terminal history. When a project rule asks for a setup document too, write it, and make its first step "run scripts/<name>.sh". The document points at the script; it never replaces it.
The UX is already built in assets/template.sh (stage progress, confirm gates, cross-platform URL opening including WSL, hidden secret entry, idempotent .env upserts, a refusal to write secrets into an .env that git does not ignore, gh secret/gh variable writes, closing summary). The job is only to scope the procedure and author its stages. Never hand-edit the library above the STAGES marker; that sameness across wizards is the point.
When to Use
- "Set up the keys/secrets/env for this project", "walk me through deploying", "I just cloned this, get me running"
- A workflow file references
secrets.*orvars.*that do not exist yet - A migration or cutover with manual, irreversible steps in a vendor console
Not for steps the agent can perform itself (run them), or a single value the user can paste in one line.
Process
1. Scope from the repo, then confirm
Read before asking: .env.example, .env.*, README, docker-compose*, framework config, and every .github/workflows/*. Each secrets.X and vars.X is a value the wizard must produce. For a migration: current state, target state, and the irreversible actions between them.
Show the user the ordered stages and the values each produces; they may add, drop or reorder.
Done when, for every captured value, you know (a) where the human gets it, (b) where it is written: .env, set_secret, set_var, several, or nowhere, and (c) whether it is secret (ask_secret) or public (ask).
What ships with it
2 files 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.
- 11d ago First seen · 65 lines · 92 tokens per session scan A e89665d0d319
wizard is a skill published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 92 tokens to every session and 1,192 once invoked, about $0.0004 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-10-07.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
ci-fixer
CI failures - read error, minimal fix, verify.