Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ItIsMixian/Orrery/plugin install project-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/project-orrery)<a href="https://agentmods.dev/skills/itismixian/orrery/project-orrery"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/project-orrery/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/skills/itismixian/orrery/project-orrery"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/project-orrery.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.00049 | $0.00516 |
| Opus 5 | $0.00024 | $0.00258 |
| Sonnet 5 | $0.00010 | $0.00103 |
| 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- project-orrery — 88% identical, 22 lines differ
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 Claude Code Adapter
This is a thin Claude Code Plugin Skill. 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
python -X utf8 "${CLAUDE_PLUGIN_ROOT}/scripts/check_cli_dependency.py". If the check exits nonzero, report its structured 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 "${CLAUDE_PLUGIN_ROOT}/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 Plugin 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 requests managed Observatory
updates 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 Claude-specific files.
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.
- 12d ago First seen · 44 lines · 49 tokens per session scan A aecfc7d19d65
project-orrery is a skill published in the GitHub repository ItIsMixian/Orrery (45 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 516 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…