aoh: Skill for Claude Code

.claude/skills/planning-context/SKILL.md

planning-context is a skill for Claude Code from agenticdevops/aoh. It costs 73 tokens per session (521 once invoked), scanned A, original, MIT.

A session-memory guide for repositories that have a `.planning/` directory, where project state is kept in markdown files. It explains how to restore the plan at the start and save progress at the end.

In plain words
What is it for?
Use it to resume work, check the roadmap and current state, update planning documents, and leave a handoff for the next session.
Why use it?
It prevents important project context from being lost when a conversation is cleared or interrupted.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is agenticdevops/aoh's own configuration. It tells Claude Code how to work on aoh itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aoh configures →

Reuse

Borrowing it

Nothing to install: this file belongs to agenticdevops/aoh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/agenticdevops/aoh/main/.claude/skills/planning-context/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/agenticdevops/aoh

Made for: Claude Code.

Wrote 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.

agentmods badge for planning-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/agenticdevops/aoh/planning-context/github.svg)](https://agentmods.dev/skills/agenticdevops/aoh/planning-context)
Your own site
<a href="https://agentmods.dev/skills/agenticdevops/aoh/planning-context"><img src="https://agentmods.dev/badge/skills/agenticdevops/aoh/planning-context/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for planning-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/agenticdevops/aoh/planning-context"><img src="https://agentmods.dev/badge/skills/agenticdevops/aoh/planning-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 521 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.00521
Opus 5.5 $0.00029 $0.00208
Sonnet 5.5 $0.00015 $0.00104
Haiku 4.5 $0.00007 $0.00052

Measured 2mo ago against content hash 01539705193b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

planning-context 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 2mo 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.

.claude/skills/planning-context/SKILL.md · 45 lines

What it actually says

Planning Context — External Project Memory

Project state lives in .planning/ markdown files, NOT in the context window. Conversation memory is disposable; these files are not. Emulates GSD's .planning/ layout (stay format-compatible) but without GSD process ceremony — superpowers drives the actual work loop.

On session start (or after /clear, compaction, "resume")

Read in order:

  1. .planning/STATE.md — position, next action, session log, handoff notes
  2. .planning/ROADMAP.md — milestones, phases, statuses, definition of done
  3. .planning/PROJECT.md — vision, constraints, decisions table (never re-litigate a decided question; propose a new decision row instead)
  4. As needed: .planning/design/ (dated design docs), .planning/codebase/ (maps), .planning/todos/pending.md (small items)

If chat context and .planning/ disagree, .planning/ wins until the user overrides.

On session close, milestone, or before any risky/large change

Write back BEFORE ending:

  • STATE.md — update Position + Next action; append dated session-log entry (3-6 bullets: what happened, what changed, what's blocked)
  • ROADMAP.md — flip phase statuses; add newly discovered phases to parking lot
  • PROJECT.md — append new decisions: date, decision, why
  • todos/pending.md — add/check off small items
  • Commit .planning/ changes together with the code they describe

Rules

  • Additions over rewrites: append to session log, never erase history
  • Decisions need a "why" — a decision without rationale gets re-litigated
  • Convert relative dates ("yesterday") to absolute (2026-07-14) when writing
  • Keep entries terse and factual; this is memory, not documentation
  • If .planning/ doesn't exist yet, offer to bootstrap it with PROJECT.md, ROADMAP.md, STATE.md seeded from the current conversation
Changes

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.

  1. 2mo ago First seen · 45 lines · 73 tokens per session scan A 01539705193b

Subscribe to this mod's changes

planning-context is a skill published in the GitHub repository agenticdevops/aoh (7 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 521 once invoked, about $0.0003 per session on Opus 5.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.

Related

planning-context compared with skills from other repositories

planning-context next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
planning-contextagenticdevops/aohSkill73mo agoMITA73Claude Code
agent-v3-memory-specialistruvnet/rufloSkill81kyesterdayMITA25Claude Code
agent-swarm-memory-managerruvnet/rufloSkill81kyesterdayMITA21Claude Code
agent-collective-intelligence-coordinatorruvnet/rufloSkill81kyesterdayMITA29Claude Code
agent-memory-coordinatorruvnet/rufloSkill81kyesterdayMITA19Claude Code
memory-managementruvnet/rufloSkill81kyesterdayMITA95Claude Code
awm-rsi-toolkitPrism-Shadow/penguin-harnessSkill3.2kyesterdayApache-2.0A58Claude Code, Codex