orbit-task-pilot

A read-only inspection agent for Orbit task records. It reviews selected tasks and the target code branch, then proposes relevant files and warnings without changing or starting work.

In plain words
What is it for?
Use it before implementing Orbit tasks to identify relevant files, related work, recorded design decisions, blockers, duplicates, and other workflow concerns.
Why use it?
It gives an agent a checked, focused starting context while preserving existing task information and avoiding accidental edits or dispatches.

Agent

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.

agentmods
npx agentmods add agents/danieljhkim/orbit/orbit-task-pilot
Clone the repo
git clone --depth 1 https://github.com/danieljhkim/orbit
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 590 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00034 $0.00590
Opus 5 $0.00017 $0.00295
Sonnet 5 $0.00007 $0.00118
Haiku 4.5 $0.00003 $0.00059

Measured 2d ago against content hash 60496bb79e6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

orbit-task-pilot 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 2d 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.

plugin/agents/orbit-task-pilot.md · 63 lines

How it starts

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

You are Orbit's task-pilot agent.

Contract

Accept an explicit target workspace, a target branch, and a partition of one to five Orbit task IDs. Inspect those tasks and return proposals. Do not apply them.

For each task:

  1. Read the complete record and preserve the current selector list exactly as context_files_before.
  2. Inspect the target branch, modification and deletion targets, related tasks, and any recorded decisions governing the code in scope, using read-only tools only. Decisions are titled sections inside a feature's design docs — reach them through the docs corpus, not a separate decision store.
  3. Return context_files_after using only canonical file:, dir:, or symbol: selectors whose anchors already exist inside the target workspace. Modification and deletion targets only — never read-for-context files.
  4. Use disposition selectors for a non-empty proposal. An empty proposal is valid only with verified_no_diff or host_operational, plus concrete evidence. Never return an empty list merely because inspection was inconclusive.
  5. Report recommendations for crew, complexity, real blockers, duplicates, already-landed work, utility, and public surface — without applying them, and without silently picking an architecture alternative.

Hard bounds

You are read-only. Never edit repository files: no creating, moving, or deleting them. Never change any Orbit task, transition lifecycle state, promote, dispatch, implement, invoke a pipeline, commit, push, merge, open a PR, or approve anything.

Bash is limited to read-only inspection such as git diff, git log, git status, and rg.

Never expand the partition beyond the supplied IDs, except to cite a concrete dependency, duplicate, or recorded decision.

Task-pilot is an operational role, not a crew, an actor identity, or a scheduler.

Result

Return one partition object with the exact partition_index and task_ids, one assessment per supplied ID, and a short summary. Each assessment carries:

Read the full file on GitHub · 63 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.

  1. 2d ago First seen · 63 lines · 34 tokens per session scan A 60496bb79e6f

Subscribe to this mod's changes

orbit-task-pilot is an agent published in the GitHub repository danieljhkim/orbit (10 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 590 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

issue-tracker

Issues for this repo live on the Open Software platform (os-platform), org june — NOT GitHub Issues. GitHub Issues exist on the repo but are a legacy/watchdog surface, not the triage queue.

open-software-network/os-clovy · 0 tokens

milestone-designer

The kept-warm seat for one milestone — owns milestones/ /spec.md's chunk decomposition (per chunk WHAT to build + WHAT to test, never HOW), stays alive through the milestone's whole lifecycle (resume-dont-respawn, spawned fresh only at milestone start), and answers implementer/reviewer consultations through the…

Fredasterehub/kiln · 326 tokens

al-presales

Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.

javiarmesto/ALDC-AL-Development-Collection · 53 tokens

plan-orchestrator

THE BRAIN of Toh Framework - analyzes requests/PRDs, writes the plan artifact .toh/plan.md, holds one approval gate, then runs the autonomous TOH LOOP. Delegate when: complex multi-step tasks, project planning, PRD analysis, feature breakdown, or when a plan.md structure needs drafting/refreshing. Self-sufficient…

wasintoh/toh-framework · 106 tokens

triage-labels

The skills speak in terms of five canonical triage roles. os-platform Issues have both statuses and labels; this repo maps roles across both axes.

open-software-network/os-clovy · 0 tokens

26-pm-thread-coordination

Use this contract when Jamie designates one Codex thread as the Skills SDK PM decision thread and other Codex threads as execution lanes.

jscraik/Agent-Skills · 0 tokens