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/rainnystone/skill-orchestration-system/agents-mdgit clone --depth 1 https://github.com/Rainnystone/skill-orchestration-systemWrote 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/rainnystone/skill-orchestration-system/agents-md)<a href="https://agentmods.dev/instructions/rainnystone/skill-orchestration-system/agents-md"><img src="https://agentmods.dev/badge/instructions/rainnystone/skill-orchestration-system/agents-md.svg" alt="Measured on agentmods" 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.01531 | $0.01531 |
| Opus 5 | $0.00766 | $0.00766 |
| Sonnet 5 | $0.00306 | $0.00306 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
skill-orchestration-system 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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Project Overview
Skill Orchestration System (SOS) is a Python CLI for organizing agent skills into
auditable, activatable packs. It scans skill folders, proposes functional packs,
writes reviewable plans, applies migrations only with explicit confirmation,
generates sos-* pointer skills, and creates backups before writes.
This is the canonical public repository. Public files must stay free of personal paths, private workspace details, tokens, account data, and local planning logs. Local NHK, planning, spec, and archive surfaces may exist in this checkout, but they are intentionally ignored by Git.
Workspace Navigation
Start with the smallest current surface that can route the task safely:
AGENTS.mdfor stable execution rules.coding-agent-guide.mdfor local task routing, when present.documentation-governance.mdfor local active/archive rules, when present.task_plan.md,findings.md, andprogress.mdonly when they are active.README.md,README_CN.md,references/,src/, andtests/for public product work.
Ignored local workflow files include task_plan.md, progress.md,
findings.md, coding-agent-guide.md, documentation-governance.md, docs/,
and archive/. They are useful for local continuity but must not be committed.
Architecture Boundaries
- CLI writes must stay deterministic, auditable, and dry-run-first.
scan,propose, and dry-run commands must not mutate active skill roots.- Config, manifest, vault, backup, restore, sync, and source deletion behavior must be covered by tests.
- Source deletion must remain opt-in and require explicit confirmation.
- Pointer skills should remain short routing surfaces; full skill content belongs in the managed vault.
- Do not hardcode local absolute paths or user-specific defaults.
- Host-specific disable behavior must stay isolated to operation kinds (
MOVE_TO_ARCHIVEfor Claude,DISABLE_CODEX_SKILLfor Codex) and validated inapply._validate_planbefore any write.
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.
- 5d ago First seen · 137 lines · 1,531 tokens per session scan A 75e493cc54fb
skill-orchestration-system AGENTS.md is an instructions file published in the GitHub repository Rainnystone/skill-orchestration-system (10 stars, last pushed 2mo ago), licensed MIT. It adds 1,531 tokens to every session, about $0.0077 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
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).