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.
curl -O https://raw.githubusercontent.com/openclosed-org/axum-harness/main/.agents/skills/planner/SKILL.mdgit clone --depth 1 https://github.com/openclosed-org/axum-harnessWrote 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/openclosed-org/axum-harness/planner)<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="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.00073 | $0.00750 |
| Opus 5 | $0.00036 | $0.00375 |
| Sonnet 5 | $0.00015 | $0.00150 |
| Haiku 4.5 | $0.00007 | $0.00075 |
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 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 — 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 --stator routing metadata - Consult
agent/codemap.ymland 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) |
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 · 96 lines · 73 tokens per session scan A 3bc61b1c3f3b
planner is a skill published in the GitHub repository openclosed-org/axum-harness (49 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 750 once invoked, about $0.0004 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
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
microservices-expert
Expert-level microservices architecture, patterns, service mesh, and distributed systems. Use when the user mentions distributed systems, service mesh, or architecture, or when the task involves Microservices Principles, Architecture Patterns, Communication, or Data Management.
microservices-patterns
Generate and review microservices code using patterns from Chris Richardson's "Microservices Patterns." Use this skill whenever the user asks about microservices architecture, wants to generate service code, design distributed systems, review microservices code, implement sagas, set up CQRS, configure API gateways…
distributed-feasibility-checker
Evaluate whether a system should adopt distributed architecture by systematically checking against the 8 Fallacies of Distributed Computing and assessing team/operational readiness. Use this skill whenever the user is considering microservices, debating monolith vs distributed, hearing "let's use microservices,"…
docker-local-build
Build and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.