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 skills add ItIsMixian/Orrery --skill skill-entry-router-v0.1git 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/skill-entry-router-v0.1)<a href="https://agentmods.dev/skills/itismixian/orrery/skill-entry-router-v0.1"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/skill-entry-router-v0.1/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/skill-entry-router-v0.1"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/skill-entry-router-v0.1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00481 |
| Opus 5 | $0.00018 | $0.00241 |
| Sonnet 5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
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 11d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Orrery
Keep one traceable fact chain without making every task carry every Orrery operation.
Route before loading detail
- Existing-project maintenance or audit: obey the target
AGENTS.md; read its mandatory entrances, relevant State Docs, effective ADRs only when reasons are needed, and the active Implementation Plan before implementation. Do not load install, release, migration, or viewer references unless the task actually crosses those boundaries. - New scaffold: read scaffold.md.
- Skill update, viewer upgrade, or compatibility work: read release-channel.md and migration-contract.md.
- Architecture explanation or document-schema migration: read architecture.md and migration-contract.md.
- Run or configure the observatory: read viewer.md.
Always preserve these boundaries
- Seed constrains durable principles; ADR records accepted choices and reasons; approved Design specifies them; Plan records intent; code/configuration/assets/external state are implementation truth; State Docs report current facts; Validation records reproducible evidence.
acceptedis notimplemented; a worktree change is not a commit; a commit is not a release.- Never bulk-overwrite authored
AGENTS.mdordocs/. Default installation creates missing files only; managed-tool upgrades require a reviewed dry run and backup. - Never package credentials,
ai-config.json, keyring contents, caches,.port, generateddocs/_site/, virtual environments, or user-specific benchmark output. - Dashboards, AI answers, summaries and radar are projections, not new project facts.
Close maintenance work
Validate in proportion to the changed boundary and follow the target Plan/AGENTS commands. After real implementation or validation, update affected State Docs and PROGRESS, append DEVLOG, and refresh HANDOFF when the stopping point or risks changed. Report implementation, commit, push and release status separately.
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.
- 11d ago First seen · 43 lines · 36 tokens per session scan A 1153e1c6dec4
project-orrery is a skill published in the GitHub repository ItIsMixian/Orrery (45 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 481 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…