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/ariaxhan/kernel-claude/helpnpx skills add ariaxhan/kernel-claude --skill helpgit clone --depth 1 https://github.com/ariaxhan/kernel-claudeWhat 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.01871 |
| Opus 5 | $0.00017 | $0.00936 |
| Sonnet 5 | $0.00007 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
help 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<host_invocation>
Claude Code invokes skills as /kernel:<name>. Codex invokes them as
$kernel:<name>. Tables below use Claude Code syntax; Codex users replace the
leading slash with a dollar sign.
</host_invocation>
<on_start> Before showing help, check the actual state of the plugin as loaded in your context:
- Is the session-start hook output visible? (Look for "# KERNEL" at conversation start)
- Which profile is active? (local, github, github-oss, github-production)
- Are there active contracts or pending reviews in AgentDB?
- Report what you see, don't just recite docs.
agentdb recall "<feature> <subsystem> <files/symbols> <error/outcome>" --global
</on_start>
<getting_started>
| What you want | What to type |
|---|---|
| Set up a new project | /kernel:init |
| Start working on anything | /kernel:ingest + describe task |
| Run autonomously overnight | /kernel:forge + describe goal |
| Explore approaches creatively | /kernel:dream + describe problem |
| Debug something broken | /kernel:diagnose + describe symptom |
| Save progress before stopping | /kernel:handoff |
| </getting_started> |
<skills_reference>
Core Workflow (kind: workflow)
| Skill | Purpose | When to use |
|---|---|---|
/kernel:ingest |
Guided entry, classify, scope, execute | Default for any task. Human confirms each phase. |
/kernel:forge |
Autonomous engine, heat/hammer/quench/anneal | Run overnight. Iterates until antifragile or reports why not. |
/kernel:dream |
Creative exploration, 3 perspectives + stress test | When you need competing approaches before committing. |
/kernel:diagnose |
Systematic debugging + refactor analysis | Bugs, regressions, or before refactoring. Diagnosis before prescription. |
/kernel:simplify |
Cut cyclomatic complexity, measured by lizard, verified by re-measure | Jungle code, god functions, after any AI-written branchy function. A number, not an opinion. |
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 · 165 lines · 34 tokens per session scan A 6814b738d5d3
help is a skill published in the GitHub repository ariaxhan/kernel-claude (12 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,871 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
prolong
Recover and use durable coding-session history from PRO-LONG's local append-only log. Use on long-running coding tasks, after context compaction or session resume, when reconstructing prior decisions or tool results, or before repeating work that may already have been attempted.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
causal-memory
Causal memory for agents — install/setup the causal-memory MCP server, then record decisions/outcomes and recall them before acting. Trigger when the user asks to install or set up causal-memory/agent memory, when causal-memory MCP tools are available and the agent faces a non-trivial decision (architecture, debugging…
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
a0-review-plugin
Full audit of Agent Zero plugins in usr/plugins/. Reviews manifest validity, directory structure, code patterns (Store Gating, notifications, imports), security, and duplicate detection against the community index. Use when asked to review, audit, validate, or check an existing plugin before using or contributing it.
create-skill
Wizard for creating new Agent Zero skills. Guides users through creating well-structured SKILL.md files. Use when users want to create custom skills.