agent-planners

agent-planners is a skill for Claude Code, Codex from NicolaiLassen/orxhestra. It costs 29 tokens per session (402 once invoked), scanned A, original, Apache-2.0.

A set of planning components for orxhestra agents, a Python framework for building software agents. They can add step planning, structured planning sections, or a task board stored in the agent's context.

In plain words
What is it for?
Use them when building agents that need plans before tool calls, explicit planning and final-answer sections, or task status tracking.
Why use it?
They help an agent organise multi-step work and keep track of tasks instead of handling every request as an unstructured exchange.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use them when building agents that need plans before tool calls, explicit planning and final-answer sections, or task status tracking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nicolailassen/orxhestra/agent-planners
Install

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.

Any agent
npx skills add NicolaiLassen/orxhestra --skill agent-planners
Clone the repo
git clone --depth 1 https://github.com/NicolaiLassen/orxhestra

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.

agentmods badge for agent-planners

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicolailassen/orxhestra/agent-planners/github.svg)](https://agentmods.dev/skills/nicolailassen/orxhestra/agent-planners)
Your own site
<a href="https://agentmods.dev/skills/nicolailassen/orxhestra/agent-planners"><img src="https://agentmods.dev/badge/skills/nicolailassen/orxhestra/agent-planners/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 agent-planners

Your own site · 80×15
<a href="https://agentmods.dev/skills/nicolailassen/orxhestra/agent-planners"><img src="https://agentmods.dev/badge/skills/nicolailassen/orxhestra/agent-planners.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 402 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.00029 $0.00402
Opus 5 $0.00015 $0.00201
Sonnet 5 $0.00006 $0.00080
Haiku 4.5 $0.00003 $0.00040

Measured 12d ago against content hash 093884f3a5f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

agent-planners 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 12d 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.

docs/skills/agent-planners/SKILL.md · 64 lines

What it actually says

Agent Planners

Planners inject planning instructions into the system prompt before each LLM call.

Custom planner

from orxhestra import BasePlanner, ReadonlyContext, LlmRequest, LlmResponse

class MyPlanner(BasePlanner):
    def build_planning_instruction(
        self, ctx: ReadonlyContext, request: LlmRequest
    ) -> str | None:
        return "Think step by step before acting. Plan before calling tools."

    def process_planning_response(
        self, ctx: ReadonlyContext, response: LlmResponse
    ) -> LlmResponse | None:
        return None  # no post-processing needed

PlanReActPlanner

Enforces structured planning tags — the agent must emit /*PLANNING*/ and /*FINAL_ANSWER*/ blocks.

from orxhestra import PlanReActPlanner, LlmAgent

agent = LlmAgent(
    name="PlanningAgent",
    model=model,
    tools=[...],
    planner=PlanReActPlanner(),
)

TaskPlanner

Maintains a task board in ctx.state and injects status into the system prompt. Pairs with ManageTasksTool.

from orxhestra import TaskPlanner, LlmAgent

planner = TaskPlanner()

agent = LlmAgent(
    name="ProjectAgent",
    model=model,
    tools=[planner.get_manage_tasks_tool()],
    planner=planner,
    instructions=(
        "Track your work with manage_tasks. "
        "Initialize tasks at the start. Mark each complete when done."
    ),
)

The agent calls manage_tasks with actions: initialize, list, create, update, complete, remove.

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. 12d ago First seen · 64 lines · 29 tokens per session scan A 093884f3a5f2

Subscribe to this mod's changes

agent-planners is a skill published in the GitHub repository NicolaiLassen/orxhestra (21 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 402 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.

Related

Other skills, from other repositories

ampersend

Give an agent a way to pay for things on the internet. Use when the user wants the agent to be able to pay for things online, when an HTTP call returns 402 Payment Required, when calling an endpoint that charges per request, when the user names a capability they want without a specific URL in mind, or when the user is…

edgeandnode/ampersend-sdk · 80 tokens

unit-converter

Converts values between metric and imperial units, using the project's agreed factors.

polymind-inc/agent-framework-js · 19 tokens

agent-framework-py-release

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…

microsoft/agent-framework · 103 tokens

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens

build-and-test

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.

microsoft/agent-framework · 26 tokens

python-feature-lifecycle

Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.

microsoft/agent-framework · 43 tokens