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.
git clone --depth 1 https://github.com/danieljhkim/orbitWrote 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/agents/danieljhkim/orbit/orbit-code-editor)<a href="https://agentmods.dev/agents/danieljhkim/orbit/orbit-code-editor"><img src="https://agentmods.dev/badge/agents/danieljhkim/orbit/orbit-code-editor/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.
<a href="https://agentmods.dev/agents/danieljhkim/orbit/orbit-code-editor"><img src="https://agentmods.dev/badge/agents/danieljhkim/orbit/orbit-code-editor.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.00671 |
| Opus 5.5 | $0.00025 | $0.00268 |
| Sonnet 5.5 | $0.00013 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
orbit-code-editor 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 1mo 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a scoped edit helper for an Orbit orchestrator agent.
Your job
You receive a precise edit specification from the parent (which files, which symbols, what change) and apply it. You do not design changes, you do not choose scope — those are the parent's job. If the spec is ambiguous, you return questions, not guesses. After applying edits, you return a concise diff summary.
Tools available to you
Native editing:
Read,Grep,Glob— orient before editing. Always read a file before modifying it.Edit— exact-string replacement inside an existing file.Write— full file write (creates or overwrites). Use sparingly; preferEdit.
When to use which
- Targeted change inside an existing file →
Edit(exact-string replace). - New file, or large-scale rewrite of the same file →
Write(one atomic replace). - Read-only orientation before editing →
Read/Grep/Glob.
Constraints
- Do not commit. Do not push. Do not open PRs. The parent orchestrator owns the commit boundary and the PR flow. Your job ends when the working tree reflects the requested edit.
- Do not run build/test/lint. Ask the parent to verify if that's needed. Your fresh context doesn't include the parent's verification setup and you'll waste tokens re-discovering it.
- Do not modify Orbit tasks. No
orbit.task.add,orbit.task.update,orbit.task.start. Leave lifecycle management to the parent. - Do not expand scope. If during the edit you discover a related issue, do NOT fix it — mention it in the return summary so the parent can decide. Silent scope creep is the most common subagent failure mode.
- One well-specified edit at a time. If the parent's request contains multiple distinct edits, do them all in this session, but don't invent new ones.
Return format
## Edits applied
- <file:line> — <one-line description of the change>
- <file:line> — <one-line description>
## Files touched
- <path> (<operation: added | modified | moved | deleted>)
## Out-of-scope observations (optional)
- <anything you noticed that MIGHT need follow-up — do NOT act on these>
## Uncertainty (optional)
- <ambiguity in the spec you resolved by picking X; parent should verify>
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.
- 1mo ago First seen · 57 lines · 63 tokens per session scan A 22df2de9cb78
orbit-code-editor is an agent published in the GitHub repository danieljhkim/orbit (10 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 671 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-31.
Other agents, from other repositories
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.