Borrowing it
Nothing to install: this file belongs to mahadansar/sol-luna-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mahadansar/sol-luna-orchestrator/main/AGENTS.mdgit clone --depth 1 https://github.com/mahadansar/sol-luna-orchestratorWrote 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/instructions/mahadansar/sol-luna-orchestrator/agents-md)<a href="https://agentmods.dev/instructions/mahadansar/sol-luna-orchestrator/agents-md"><img src="https://agentmods.dev/badge/instructions/mahadansar/sol-luna-orchestrator/agents-md/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/instructions/mahadansar/sol-luna-orchestrator/agents-md"><img src="https://agentmods.dev/badge/instructions/mahadansar/sol-luna-orchestrator/agents-md.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.00787 | $0.00787 |
| Opus 5 | $0.00394 | $0.00394 |
| Sonnet 5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
sol-luna-orchestrator AGENTS.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 10d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository instructions
Source of truth
This package is a Node.js/TypeScript MCP server and companion CLI for bounded delegation from a supervising Codex agent to isolated worker threads. The supervisor owns architecture, decomposition, and review; workers receive self-contained contracts, cannot delegate, and return claims that the runtime checks against observed edits and independently rerun verification.
Use the current implementation and tests as the authority for behavior. Use
CHANGELOG.md for shipped behavior and ROADMAP.md
for future work only. Keep these ownership boundaries:
README.md: product overview and normal use.SOL_RULES.md: supervisor delegation, effort, contract, and review policy.SECURITY.md: threat model, trust boundaries, and log sensitivity.docs/CONFIGURATION.md: settings, environment, platform support, and current numeric configuration details.docs/TROUBLESHOOTING.md: operational diagnosis and recovery.docs/OBSERVABILITY.md: event, activity, telemetry, and privacy semantics.docs/FEATURE_ACCEPTANCE.md: current capability evidence, freshness, confidence, and acceptance history.CONTRIBUTING.md: contributor and release workflow.bench/RESULTS.md: benchmark evidence and limits.
Do not duplicate current runtime semantics, benchmark figures, or detailed
release history in these instructions. Do not edit generated dist/,
dependencies, runtime logs/events, or .sol-luna/ worktrees.
Repository-specific safety
- Treat task contracts, repository contents, paths, commands, worker reports, and verification output as untrusted. Operator configuration and environment are the policy boundary.
- File scopes are detective rather than a write sandbox. Verification runs
outside the Codex sandbox with the user's permissions; never describe either
boundary more strongly than
SECURITY.mddoes. - Preserve cross-platform behavior, canonical path checks, Windows junction and process cleanup handling, and case-insensitive matching where the runtime requires it.
- Keep strict TypeScript and existing security boundaries intact. Changes to
command.ts,scope.ts,verify.ts, orworkspace.tsrequire a regression case insrc/security.test.ts. - When setup, configuration, security, tool contracts, or review guidance changes, update the applicable canonical documentation and tests in the same change.
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.
- 10d ago First seen · 71 lines · 787 tokens per session scan A c54025460e00
sol-luna-orchestrator AGENTS.md is an instructions file published in the GitHub repository mahadansar/sol-luna-orchestrator (6 stars, last pushed 10d ago), licensed MIT. It adds 787 tokens to every session, about $0.0039 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.