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 agentmods add skills/yuanchuan/aivo/createnpx skills add yuanchuan/aivo --skill creategit clone --depth 1 https://github.com/yuanchuan/aivoWrote 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/yuanchuan/aivo/create)<a href="https://agentmods.dev/skills/yuanchuan/aivo/create"><img src="https://agentmods.dev/badge/skills/yuanchuan/aivo/create.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.00087 | $0.02346 |
| Opus 5 | $0.00044 | $0.01173 |
| Sonnet 5 | $0.00017 | $0.00469 |
| Haiku 4.5 | $0.00009 | $0.00235 |
Grade A, and why
create-skill 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 yesterday.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Skill
This is the guided workflow for building new aivo skills and iteratively improving them. Your job is to figure out where the user is in the process and jump in to move them forward — sometimes that's "I want a skill for X" (start from scratch), sometimes it's "here's a draft, help me sharpen it" (go straight to review/iterate).
What a skill is
A skill is a folder holding a SKILL.md with YAML frontmatter (name, description) and a Markdown body of instructions. aivo discovers skills from these roots (project shadows user; first name wins):
- Project:
./.agents/skills,./.aivo/skills,./.claude/skills - User:
~/.agents/skills,~/.config/aivo/skills,~/.claude/skills
~/.config/aivo/skills/<name>/ is the dir aivo owns and the one /skills add scaffolds into; /skills add -p (or --project) targets the repo's ./.agents/skills instead — for skills meant to ship with the project (note: the agent advertises repo-local skills as untrusted content). Discovery is on-demand, so a skill you create is usable immediately — no restart: the user can run it with /<name> right away, it shows up in /skills, and the model starts offering it (via the skill tool) from the next turn on.
skill-name/
├── SKILL.md (required: frontmatter + instructions)
└── (optional bundles)
├── scripts/ executable helpers for deterministic/repetitive work
├── references/ docs the model reads into context as needed
└── assets/ templates/icons/fonts used in output
Step 1 — Capture intent
Understand what the user wants before writing anything. The current conversation may already contain the workflow to capture ("turn this into a skill") — mine it for the tools used, the step sequence, the corrections the user made, and the input/output formats. Then confirm:
- What should this skill let the agent do?
- When should it trigger — what user phrases and contexts?
- What's the expected output (format, files, side effects)?
- Does it need bundled scripts/references, or is it pure instructions?
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.
- yesterday First seen · 118 lines · 87 tokens per session scan A 499d75bc9d04
create-skill is a skill published in the GitHub repository yuanchuan/aivo (192 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 2,346 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-bulk-edit-classification
Recognize when a mission is a bulk edit and drive the occurrence-classification guardrail on the user's behalf. Triggers: user says any variant of "rename X to Y", "change the terminology", "migrate all occurrences", "replace across the codebase", "the X feature is now the Y feature", "sed everywhere", or any request…
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…