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/noirewinter/hplan/hplan-openclawnpx skills add Noirewinter/hplan --skill hplan-openclawgit clone --depth 1 https://github.com/Noirewinter/hplanWrote 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/noirewinter/hplan/hplan-openclaw)<a href="https://agentmods.dev/skills/noirewinter/hplan/hplan-openclaw"><img src="https://agentmods.dev/badge/skills/noirewinter/hplan/hplan-openclaw.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.00100 | $0.02351 |
| Opus 5 | $0.00050 | $0.01175 |
| Sonnet 5 | $0.00020 | $0.00470 |
| Haiku 4.5 | $0.00010 | $0.00235 |
Grade A, and why
hplan 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 5d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hplan — Hierarchical Persistent Planning
Use the file system as persistent working memory for complex multi-phase tasks. This skill solves two problems that arise in long task executions:
- Goal drift — the agent gradually forgets the original objective as the work progresses
- Spec loss — detailed requirements, deliverables, and dependencies vanish from context
Core Idea
Context window = RAM (volatile, limited)
File system = Disk (persistent, unlimited)
Memory system = Long-term recall (cross-session, searchable)
→ Task structure and specs go to .plan/ (file system)
→ Key milestones and decisions go to memory (MEMORY.md / daily notes)
→ The overview stays concise for quick re-reading
→ All three layers work together to prevent drift and loss
.plan/ Directory Structure
All plan files are stored in the .plan/ directory under the current workspace:
.plan/
├── overview.md ← Global summary (≤25 lines, re-read frequently)
├── decisions.md ← Decision log
├── errors.md ← Error log
└── phases/
├── phase1_xxx/
│ ├── spec.md ← Detailed spec for this phase
│ └── checklist.md ← Item-by-item completion status
├── phase2_xxx/
│ └── ...
└── ...
Use the templates in templates/ as starting points for each file. Always use relative paths (.plan/...) when reading and writing plan files.
Integration with OpenClaw Memory
hplan uses the file system for structured task data (.plan/ directory) and OpenClaw's memory system for cross-session awareness. They serve different purposes:
| Layer | What it stores | Why |
|---|---|---|
.plan/ files |
Full specs, checklists, detailed plans | Structured, complete, not subject to compaction |
| MEMORY.md | Task goal, current phase, key decisions | Survives session restarts, loaded automatically |
| Daily notes | Progress snapshots, phase completions | Searchable history, compaction-safe via memory |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 251 lines · 100 tokens per session scan A 8b991b4ff9a9
hplan is a skill published in the GitHub repository Noirewinter/hplan (5 stars, last pushed 4mo ago), licensed MIT. It adds 100 tokens to every session and 2,351 once invoked, about $0.0005 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-31.
Other skills, from other repositories
ai-agent-builder
Expert guide for building AI-powered coding agents that produce professional-quality output. Trigger whenever the user asks to build an AI agent, coding assistant, automation pipeline, tool-using LLM system, or says "agent", "agentic", "tool use", "function calling", "LLM pipeline", "AI workflow", "coding bot", or…
agent-development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
adk-unit-design
Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to docs/design/{topic}/{unit}/index.md. It describes the code as implemented, not a proposed design, and its reader is a developer about…
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.