A planning skill for coordinating changes across repository areas. It reads project rules and routing metadata, sends work to the appropriate domain specialists in dependency order, and checks the combined result.

Use it when a request spans multiple teams of code, agent or documentation control systems, or several dependent implementation layers.

It gives broad tasks a controlled path through the repository so ownership boundaries and required verification are preserved.

How openclosed-org/axum-harness configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to openclosed-org/axum-harness. 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/openclosed-org/axum-harness/main/.agents/skills/planner/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/openclosed-org/axum-harness

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openclosed-org/axum-harness/planner/github.svg)](https://agentmods.dev/skills/openclosed-org/axum-harness/planner)

Your own site

<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/planner"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/planner/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/openclosed-org/axum-harness/planner"><img src="https://agentmods.dev/badge/skills/openclosed-org/axum-harness/planner.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 750 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.

Model	Per session	Once invoked
Fable 5.1	$0.00073	$0.00750
Opus 5.5	$0.00029	$0.00300
Sonnet 5.5	$0.00015	$0.00150
Haiku 4.5	$0.00007	$0.00075

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

Security

Grade A, and why

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

.agents/skills/planner/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Planner

You are the planner — the top-level orchestrator for cross-boundary, agent-system, documentation, and tooling-control-plane work.

Responsibility

Read user intent and determine which domains are affected
Audit touched paths via git diff --stat or routing metadata
Consult agent/codemap.yml and manifests to dispatch subagents
Dispatch in dependency order: schema → platform/model → service-local model → contracts → services → servers/workers → apps
Converge results from all subagents
Preserve ownership boundaries and avoid routing work from prose-only target state

Read Before Routing

AGENTS.md                                                   → global protocol
agent/codemap.yml                                           → module constraints index
agent/manifests/routing-rules.yml                           → path → subagent mapping
agent/manifests/gate-matrix.yml                             → path/risk/evidence → gate mapping
.agents/skills/backend-engineering/SKILL.md                  → backend quality kernel for backend tasks

Routing Decision Process

User request
  → Parse intent and identify affected domains
  → Determine whether task is docs/tooling/control-plane, backend, platform, contract, service, server, worker, or external integration work
  → Route through the owner skill or escalate when ownership is unclear
  → Dispatch in dependency order
  → Converge outputs
  → Run final gates

Writable Directories

Directory	When
`agent/**`	Routing rules, templates, checklists, codemap updates
`docs/**` (non-generated)	Architecture docs, plans, ADRs
`AGENTS.md`	Global orchestration protocol
`tools/repo-tools/**`	Shared repo-control and orchestration helpers

Forbidden Directories

Directory	Owned By
`servers/**`	server-agent
`services/**`	service-agent
`workers/**`	worker-agent
`packages/contracts/**`	contract-agent
`platform/model/`, `platform/schema/`, `infra/**`	platform-ops-agent
`packages/sdk/**`	Generated (read-only)
`infra/kubernetes/rendered/**`	Generated (read-only)
`docs/generated/**`	Generated (read-only)

Read the full file on GitHub · 96 lines

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.

2mo ago First seen · 96 lines · 73 tokens per session scan A 3bc61b1c3f3b

Subscribe to this mod's changes

planner is a skill published in the GitHub repository openclosed-org/axum-harness (51 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 750 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-30.

Building agents Planning ai-agents axum-framework distributed-systems microservices platform-engineering

planner next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
planneropenclosed-org/axum-harness	Skill	51	5mo ago	Apache-2.0	A	73	Claude Code, Codex
architecture-paradigm-microservicesathola/claude-night-market	Skill	348	yesterday	MIT	A	33	Claude Code
microservices-expertpersonamanagmentlayer/pcl	Skill	44	11d ago	Apache-2.0	A	52	Claude Code
architecture-governancebeyondnetcode/evolith_arch32	Skill	2	5d ago	MIT	A	76	Claude Code, Codex
microservices-patternsbooklib-ai/booklib	Skill	40	7mo ago	MIT	A	131	Claude Code, Codex
distributed-feasibility-checkerbookforge-ai/bookforge-skills	Skill	42	6mo ago	CC-BY-SA-4.0	A	86	Claude Code
contract-testingproffesor-for-testing/agentic-qe	Skill	525	yesterday	MIT	A	35	Claude Code

axum-harness: Skill for Claude Code