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 instructions/robdel12/orbitdock/claude-mdgit clone --depth 1 https://github.com/Robdel12/OrbitDockWhat 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.00118 | $0.00118 |
| Opus 5 | $0.00059 | $0.00059 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
OrbitDock CLAUDE.md 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 3d 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.
What it actually says
Claude Code Instructions for OrbitDock
Shared repository guidance now lives in AGENTS.md.
Use AGENTS.md as the starting point for:
- day-to-day repo guardrails
- the docs map for workflow, architecture, debugging, and persistence
- the mutation-response rule: authoritative
POST/PATCH/PUTresponses should update local state immediately, then subscriptions reconcile - links to the deeper docs in
docs/
This file remains as a compatibility pointer for tools or workflows that still look for CLAUDE.md.
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.
- 3d ago First seen · 12 lines · 118 tokens per session scan A 924920b63e34
OrbitDock CLAUDE.md is an instructions file published in the GitHub repository Robdel12/OrbitDock (95 stars, last pushed 4mo ago), licensed MIT. It adds 118 tokens to every session, about $0.0006 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 instructions, from other repositories
OnlySwitch AGENTS.md
Instructions for jacklandrin/OnlySwitch, covering onlyswitch agent guidance, workflow, context routing and project-specific working rules.
Applite CLAUDE.md
Instructions for milanvarady/Applite, covering claude.md, project overview, build & run, architecture and data flow.
Vocello AGENTS.md
Instructions for PowerBeef/Vocello, covering agents.md — vocello (qwenvoice), product and authority, start and resume work, hard invariants and domain routing.
skills-manager CLAUDE.md
Instructions for yibie/skills-manager, covering skills manager - development guide, tui engine: blessed, 核心原则, 参考文档 and 正确的 list 用法.
TokenEater CLAUDE.md
Instructions for AThevon/TokenEater: The full contributor and agent guide for this project lives in AGENTS.md: repo layout, architecture and data flow, the hard-won SwiftUI rules, and the build / test / release commands.
swift-tui AGENTS.md
Instructions for SwiftTUI/swift-tui, covering agents.md, build & test commands, architecture (one-page summary), development guidelines and code style.