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 skills/itismixian/orrery/codexnpx skills add ItIsMixian/Orrery --skill codexgit clone --depth 1 https://github.com/ItIsMixian/OrreryWrote 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/itismixian/orrery/codex)<a href="https://agentmods.dev/skills/itismixian/orrery/codex"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/codex.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 | $0.00049 | $0.00519 |
| Opus 5 | $0.00024 | $0.00260 |
| Sonnet 5 | $0.00010 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
project-orrery 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 4d 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.
This is a copy
88% identical to project-orrery — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orrery Codex Adapter
This is a thin Codex adapter. It requires the separately installed
project-orrery CLI declared in adapter-manifest.json; it does not contain
Orrery templates, schema, compatibility rules, or project facts.
Route the task
- Read the target repository's root
AGENTS.mdand follow its local reading order and safety boundaries before touching project files. - Before invoking the CLI, run this Adapter's
scripts/check_cli_dependency.pywith the Python interpreter that resolvesproject-orrery. If the check exits nonzero, report its dependency error instead of falling back to copied templates or inferred rules. - Before the first product write, run
project-orrery worktree route --target <repo> --adapter-manifest <this-adapter>/adapter-manifest.json --platform-session-id <current-session-id> --json. If the runtime does not expose its session ID, stop with the returned continuation brief. When the route requires attach, run the correspondingworktree session attachcommand and rerun the route. Continue only when the route returnsallow; never bypass dirty-primary recovery or silently rebind an existing session. - Use the CLI command that matches the request:
project-orrery scaffold --target <repo> --title <title> --dry-runproject-orrery validate --target <repo>project-orrery check-update --target <repo>
- Keep adapter installation separate from target-project scaffolding, Observatory tool upgrades, and authored-document migration.
- Never claim that an accepted decision is implemented, that an installed scaffold is integrated, or that Agent self-report proves files were read.
For established repositories, inspect existing documentation roles and review
the dry-run before any mutation. Never silently overwrite authored documents.
Only use --upgrade-tools when the user explicitly asks to update managed
Observatory files and has reviewed the planned backups.
After implementation or validation work, update the authority layers required
by the target repository's own AGENTS.md. Do not create a parallel state
summary in Codex-specific files.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 44 lines · 49 tokens per session scan A 34f6ff0ae157
project-orrery is a skill published in the GitHub repository ItIsMixian/Orrery (45 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 519 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to project-orrery, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…