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 commands/povvo/claudikins-kernel/outlinegit clone --depth 1 https://github.com/povvo/claudikins-kernelWrote 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/commands/povvo/claudikins-kernel/outline)<a href="https://agentmods.dev/commands/povvo/claudikins-kernel/outline"><img src="https://agentmods.dev/badge/commands/povvo/claudikins-kernel/outline.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.00017 | $0.02199 |
| Opus 5 | $0.00009 | $0.01099 |
| Sonnet 5 | $0.00003 | $0.00440 |
| Haiku 4.5 | $0.00002 | $0.00220 |
Grade A, and why
claudikins-kernel:outline 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 6d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claudikins-kernel:outline Command
You are orchestrating an iterative planning workflow with human checkpoints at every phase.
Flags
| Flag | Effect |
|---|---|
--session-id ID |
Resume previous session by ID |
--skip-research |
Skip Phase 2 research |
--skip-review |
Skip Phase 5 review |
--fast-mode |
60-second iteration cycles |
--timing |
Show phase durations for velocity tracking |
--list-sessions |
Show available sessions for resume |
--output PATH |
Plan destination path |
--run-verify |
Run verification anytime |
Merge Strategy
None - outputs are not merged.
Philosophy
"Planning is a conversation, not a production line." - Guru Panel consensus
- Human in the loop at every phase
- Verification available anytime (--run-verify flag)
- Pool of tools (unrestricted, not gatekept by phase)
- Defaults ON, skip flags for less
- Non-linear phase access (can jump back/forward)
- 5-7 agents per SESSION, not 30 per batch
State Management
State file: .claude/plan-state.json
{
"session_id": "plan-YYYY-MM-DD-HHMM",
"started_at": "ISO timestamp",
"project_hash": "sha256 of project dir",
"phase": "brain-jam|research|approaches|draft|review",
"research_complete": false,
"human_decisions": [],
"abandoned": false
}
Phase 0: Session Initialisation
- Read
$taskfrom user input - Check for existing sessions via
--list-sessionsor--session-id - If previous session found:
- If 4+ hours old: WARN "Session is stale. Old research may be outdated."
- Offer: [Resume] [New Plan] [Review Last]
- Create new session ID if starting fresh
- Initialise state file via session-init.sh hook
Phase 1: Brain-Jam
Load the brain-jam-plan skill for methodology.
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.
- 6d ago First seen · 348 lines · 17 tokens per session scan A c748e78e1757
claudikins-kernel:outline is a command published in the GitHub repository povvo/claudikins-kernel (126 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 2,199 once invoked, about $0.0001 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 commands, from other repositories
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
explain-architecture
Analyze and explain software architecture with ASCII diagrams and pattern detection. Creates visual representations of system design.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
history
List past OCR review sessions.
setup
Get started with ClawdBod — set your break cadence and an optional profile for calorie estimates.