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/dreamnpx skills add ariaxhan/kernel-claude --skill dreamgit clone --depth 1 https://github.com/ariaxhan/kernel-claudeWrote 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/ariaxhan/kernel-claude/dream)<a href="https://agentmods.dev/skills/ariaxhan/kernel-claude/dream"><img src="https://agentmods.dev/badge/skills/ariaxhan/kernel-claude/dream.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 | $0.00039 | $0.01704 |
| Opus 5 | $0.00019 | $0.00852 |
| Sonnet 5 | $0.00008 | $0.00341 |
| Haiku 4.5 | $0.00004 | $0.00170 |
Grade A, and why
dream 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 4d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Not "give me 3 options" — structured divergence: competing value systems + adversarial stress test + integrity scoring.
The winning approach is the one that SURVIVES attack, not the one that sounds best.
Use before any non-trivial decision. Use when the obvious answer feels too easy.
<on_start> agentdb read-start # prior dreams + learnings seed the perspectives; don't re-explore killed approaches </on_start>
<skill_load> always: skills/quality/SKILL.md, skills/architecture/SKILL.md on_domain: api: skills/architecture/reference/api.md, skills/architecture/reference/backend.md frontend: skills/frontend/SKILL.md backend: skills/architecture/reference/backend.md security: skills/tearitapart/reference/security.md </skill_load>
Dreams that ignore the codebase are fantasies, not proposals.
Target: 90% code reduction. Must reference actual files that could be deleted.
Format: 3-8 lines. Effort estimate. Coverage percentage.
Target: complete solution. Must sketch actual architecture, not hand-wave.
Format: full description with component diagram. Effort estimate.
Target: 80% solution with clear upgrade path.
Must explicitly state what's deferred and the cost of deferral.
Format: concrete plan. Effort estimate. Tradeoff table.
Tier 1: generate all 3 inline. Tier 2+: spawn dreamer agent for codebase-grounded perspectives.
<persona id="user" concern="usability, complexity, does it solve MY problem?">
Cuts through elegance. "Does it work for the person using this every day?"
</persona>
<persona id="adversary" concern="what breaks, worst case, what was missed">
Pure attack mode. Edge cases, race conditions, security holes, wrong assumptions.
If they can't find a flaw, the approach is strong.
</persona>
<persona id="operator" concern="can we ship it, can we maintain it, blast radius">
Operational reality. Deployment, monitoring, rollback, on-call burden.
Beautiful code that's hell to operate fails.
</persona>
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.
- 4d ago First seen · 196 lines · 39 tokens per session scan A e447afe5bf32
dream is a skill published in the GitHub repository ariaxhan/kernel-claude (12 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,704 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.