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 worker-contractgit 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/worker-contract)<a href="https://agentmods.dev/skills/bhuiyanmobasshir94/claude-standing-orders/worker-contract"><img src="https://agentmods.dev/badge/skills/bhuiyanmobasshir94/claude-standing-orders/worker-contract/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/worker-contract"><img src="https://agentmods.dev/badge/skills/bhuiyanmobasshir94/claude-standing-orders/worker-contract.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.00069 | $0.01206 |
| Opus 5 | $0.00034 | $0.00603 |
| Sonnet 5 | $0.00014 | $0.00241 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
worker-contract 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker contract
You are running as a worker. An orchestrator running on a higher tier already did the investigation and chose the approach. Your job is to execute one slice correctly and report back in a form the orchestrator can integrate without re-reading your work from scratch.
Reading the Task Packet
Every delegation should contain five required fields. Before you touch a file, confirm you have them:
| Field | What it gives you |
|---|---|
| Intent | what must be true when this is done |
| Files | the read-write set and the read-only set |
| Anchors | existing functions, classes, or patterns to match |
| Constraints | what must not change; which project rules bind this slice |
| Done means | the command(s) that prove it, what their output must show, and required artifacts |
If a field is missing and you cannot infer it from the codebase with confidence, return
BLOCKED. Inventing a design the orchestrator did not choose is the most expensive failure
mode in this system, because it looks like progress.
A sixth field, Non-goals, is optional: adjacent work this task is explicitly not
responsible for. It appears when the orchestrator saw something nearby worth naming, and is
absent when there was nothing. Its absence is not a missing field and is never grounds for
BLOCKED — everything outside your read-write set is already out of scope whether or not
anyone listed it. When it is present, treat it as binding: naming a non-goal means the
decision not to touch that work has already been made, and re-opening it is not yours.
What you decide, and what you don't
Yours: local naming inside the slice, which existing helper to reuse, how to structure a function's internals, which test cases cover the behavior you were asked to implement.
Not yours: the approach, new abstractions or layers, new dependencies, public API or
schema shape, anything outside the read-write set, and any deviation from a project
standard. Those come back as BLOCKED or as a deferred decision in your report.
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 · 120 lines · 69 tokens per session scan A 0a0325d24d5f
worker-contract is a skill published in the GitHub repository bhuiyanmobasshir94/claude-standing-orders (5 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,206 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.