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 pgit 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/p)<a href="https://agentmods.dev/skills/itismixian/orrery/p"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/p/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/p"><img src="https://agentmods.dev/badge/skills/itismixian/orrery/p.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.00112 | $0.01826 |
| Opus 5.5 | $0.00045 | $0.00730 |
| Sonnet 5.5 | $0.00022 | $0.00365 |
| Haiku 4.5 | $0.00011 | $0.00183 |
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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Orrery
Build a living project observatory without confusing ideas, decisions, plans, implementation, and evidence.
Select the operation
- New repository or missing docs system: scaffold Project Orrery.
- Existing docs system: audit local instructions and map existing files before installing anything.
- Viewer-only refresh: use the managed tool upgrade; do not replace authored docs.
- Documentation maintenance: follow the target repository's
AGENTS.md, then update the correct authority layer. - Architecture explanation or migration: read architecture.md and migration-contract.md.
Check the release channel
For an installed target, tell the user that the Skill is checking the stable release manifest, then run the cached checker before maintenance, migration, or viewer upgrades unless the user requested an offline-only workflow:
python <skill>/scripts/check_project_orrery_update.py --target <repo>
Use --offline when network access is unavailable or undesired. The checker is read-only, uses a 24-hour cache by default, and must not block ordinary documentation work merely because the release service is unavailable.
up_to_date: continue with the installed Skill.update_available_compatible: show the tagged release and explain that updating the Skill is separate from upgrading the target viewer. Do not install either silently.update_available_migration_required: stop automatic upgrading and read the tagged migration notes against the target's manifest and authored documents.installed_newer: preserve the installed version and do not downgrade unless the user explicitly requests it.current_incompatible: do not mutate the target; obtain a compatible Skill or write an explicit migration plan.unknown: report that compatibility could not be verified, then continue only with work that does not depend on a new release.
Treat release-manifest.json as the machine-readable release contract. The distributed Skill version, installed target toolchain version, project-manifest format, and document schema are separate dimensions. Semantic Versioning communicates release intent; direct compatibility is decided by the manifest's declared ranges.
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 · 111 lines · 112 tokens per session scan A 96bae11b985b
project-orrery is a skill published in the GitHub repository ItIsMixian/Orrery (45 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 1,826 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…