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.
npx agentmods add agents/danieljhkim/orbit/orbit-task-pilotgit clone --depth 1 https://github.com/danieljhkim/orbitWhat 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 | $0.00034 | $0.00590 |
| Opus 5 | $0.00017 | $0.00295 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
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.
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:
- Read the complete record and preserve the current selector list exactly as
context_files_before. - 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.
- Return
context_files_afterusing only canonicalfile:,dir:, orsymbol:selectors whose anchors already exist inside the target workspace. Modification and deletion targets only — never read-for-context files. - Use disposition
selectorsfor a non-empty proposal. An empty proposal is valid only withverified_no_difforhost_operational, plus concrete evidence. Never return an empty list merely because inspection was inconclusive. - 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:
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.
- 2d ago First seen · 63 lines · 34 tokens per session scan A 60496bb79e6f
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.
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.
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…
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.
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…
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.
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.