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 bhuiyanmobasshir94/claude-standing-orders --skill orchestration-onboardgit clone --depth 1 https://github.com/bhuiyanmobasshir94/claude-standing-ordersWrote 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/bhuiyanmobasshir94/claude-standing-orders/orchestration-onboard)<a href="https://agentmods.dev/skills/bhuiyanmobasshir94/claude-standing-orders/orchestration-onboard"><img src="https://agentmods.dev/badge/skills/bhuiyanmobasshir94/claude-standing-orders/orchestration-onboard/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/bhuiyanmobasshir94/claude-standing-orders/orchestration-onboard"><img src="https://agentmods.dev/badge/skills/bhuiyanmobasshir94/claude-standing-orders/orchestration-onboard.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.00050 | $0.01325 |
| Opus 5 | $0.00025 | $0.00662 |
| Sonnet 5 | $0.00010 | $0.00265 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
orchestration-onboard 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 12d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard this repository
Set up the repository in the current working directory for the orchestrator–worker
workflow. Template files live in the standing-orders repo — use $ARGUMENTS as its path if
given, otherwise try ~/dev/claude-standing-orders, and ask if neither exists.
Write nothing until step 4 is approved. This skill produces a plan first.
1. Read the repository
Use the Explore subagent so this does not fill the main context. Establish:
- language, framework, and how the source tree is laid out
- the real build, test, lint, and format commands — from the Makefile,
package.jsonscripts,pyproject.toml,justfile, or CI config, not from convention - where migrations, models or schemas, background jobs, and request handlers live
- whether a CLAUDE.md, AGENTS.md,
.cursorrules, or.github/copilot-instructions.mdalready exists, and what it says - whether
docs/changelogs/,docs/decisions/,docs/adr/, or an equivalent exists - what this system does and what breaks if it is wrong — the risk profile
2. Interview me for what the code cannot tell you
The operating-constraints section is the highest-value part of the file and the one you cannot infer. Ask me — in one batch, not one at a time — only about what you could not determine from the code:
- traffic shape: peak versus average, what spikes and when
- which paths have a user actively waiting, and which do not
- hard external limits: rate limits, quotas, third-party throttling
- which tables or collections grow without bound
- compliance or audit obligations, if any
- what a new engineer gets wrong in their first week
If I answer "not applicable" to something, drop that item rather than writing a hedge.
3. Map the templates onto this repository
From <orchestrator>/project-template/:
CLAUDE.md— fill everyFILLmarker from steps 1 and 2. Delete the guidance comments. Delete any non-negotiable that is not true here; a rule that is present but untrue teaches me to ignore the file. Keep it under ~150 lines.rules/*.md— rewrite eachpaths:list to match this repository's actual layout, verifying each glob matches real files. Delete rules that do not apply. Add a rule only if this project has a standard the templates do not cover.settings.json— merge into any existing.claude/settings.jsonrather than replacing it. Addaskentries for the destructive commands specific to this project: migrations, deploys, data backfills, anything that touches production.
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.
- 12d ago First seen · 110 lines · 50 tokens per session scan A 1b5558731e21
orchestration-onboard is a skill published in the GitHub repository bhuiyanmobasshir94/claude-standing-orders (5 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,325 once invoked, about $0.0003 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 skills, from other repositories
standards-expert
Expert-level ISO standards, quality management, compliance, and certification. Use when the user mentions ISO standards, quality management, compliance, or certification, or when the task involves Compliance & Certification, Auditing, or Continuous Improvement.
gdpr-expert
Expert in GDPR compliance, data protection, privacy by design, consent management, DPO responsibilities, and EU data regulations. Use when the user mentions privacy, data protection, compliance, consent, a DPO, or eu regulation, or when the task involves GDPR Fundamentals, Key Principles, Data Subject Rights, or…
soc2-expert
Expert in SOC 2 compliance, trust service criteria, audit preparation, controls implementation, and security frameworks. Use when the user mentions compliance, audit, trust services, AICPA, controls, or security framework, or when the task involves Trust Service Criteria, SOC 2 Types, Security Common Criteria, or…
dart-expert
Expert-level Dart, Flutter, mobile development, and cross-platform apps. Use when the user mentions Flutter, mobile, cross platform, or widgets, or when the task involves Dart Language or Flutter Framework.
lawyer-expert
Expert-level legal systems, contracts, compliance, and legal technology. Use when the user mentions legal, contracts, compliance, law, or legal tech, or when the task involves Legal Systems, Legal Technology, Compliance Frameworks, or Contract Management.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.