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/ai-swiss/base/implementnpx skills add ai-swiss/base --skill implementgit clone --depth 1 https://github.com/ai-swiss/baseWhat 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 | $0.00034 | $0.00683 |
| Opus 5 | $0.00017 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
implement 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 2d 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.
What it actually says
Implement a change
Build to the highest bar: load skills/competences/code-craft/SKILL.md and apply it to every
line. The truth plane and the change plane move together.
Steps
- Define done first. The test that proves the behaviour, the command that must go green. Without a verifiable criterion you are not coding; you are hoping.
- Work the smallest correct scope. Nothing beyond the change: no speculative config, no error handling for impossible cases, no field "for later".
- Code and spec in the same change. When behaviour changes, the
specs/current/leaf changes too (usetemplates/spec-leaf.mdfor a new chapter), or the work declares[SPEC-NEUTRAL: reason]. New IDs come fromnode tools/spec/new-id.mjs; cite them in prose, never restate their proof. - Tests are the specification. Each validated requirement = one named test that would fail
without it. Test behaviour, not implementation. Run the narrowest test that can falsify the
change; the full suite belongs to
verify. - No cohabitation. Whatever the change replaces dies in the same change. Clean up your own orphans (imports, dead code, obsolete tests) in the same diff.
- Update the visible record. A public-surface or visible-docs change adds its
[Unreleased]line toCHANGELOG.md, or declares[CHANGELOG-SKIP: reason]. - Run the adversarial pass on your own diff (the grid in
code-craft), then hand off toverify.
What you never do
- Swallow an error, add a silent fallback, or cap without announcing it.
- Leave a
[A COMPLETER]placeholder or a reference to the plan in committed code. - End on red: the change is not done until its narrowest tests pass.
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.
- 2d ago First seen · 57 lines · 34 tokens per session scan A e033fe21b92d
implement is a skill published in the GitHub repository ai-swiss/base (42 stars, last pushed 19d ago), licensed Apache-2.0. It adds 34 tokens to every session and 683 once invoked, about $0.0002 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
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
systematic-debug
4-phase root cause analysis and debugging.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
Code Review
Review a patch, diff, PR, or implementation for bugs, regressions, risky assumptions, and missing tests.
contribution-pipeline
Full issue-to-PR lifecycle with 5-phase gated pipeline. Produces contributions maintainers look forward to — project-aware, thoroughly tested, security-gated, well-documented. Skill bundle with sub-skills for security, test quality, documentation, clean-room verification, and vault integration.
hapo:hotfix
ALWAYS activate this skill when you are asked to FIX a bug, error, test failure, CI/CD issue, type error, lint error, log error, UI issue, or code problem. Uses hapo:debug for evidence-first diagnosis before any code change.