Agent SOP is a collection and format for writing reusable, parameterized natural-language procedures that guide AI agents through complex multi-step work. Teams use these standard operating procedures for tasks such as codebase analysis, project planning, system design, and code implementation. The catalogue add-ons distribute or apply these workflows through agent skills, plugins, and related interfaces.
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 strands-agents/agent-sop --skill agent-sop-authorgit clone --depth 1 https://github.com/strands-agents/agent-sopWrote 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/strands-agents/agent-sop/agent-sop-author)<a href="https://agentmods.dev/skills/strands-agents/agent-sop/agent-sop-author"><img src="https://agentmods.dev/badge/skills/strands-agents/agent-sop/agent-sop-author/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/strands-agents/agent-sop/agent-sop-author"><img src="https://agentmods.dev/badge/skills/strands-agents/agent-sop/agent-sop-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.03020 |
| Opus 5 | $0.00020 | $0.01510 |
| Sonnet 5 | $0.00008 | $0.00604 |
| Haiku 4.5 | $0.00004 | $0.00302 |
Grade A, and why
agent-sop-author 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent SOP Author
Overview
Agent SOPs (Standard Operating Procedures) are markdown-based instruction sets that guide AI agents through sophisticated workflows using natural language, parameterized inputs, and constraint-based execution. This skill teaches you how to create (or update), structure, and validate Agent SOPs that work across different AI systems.
Usage
When working with Agent SOPs and need to:
- Create new workflow automation SOPs
- Update existing workflow automation SOPs
- Structure multi-step agent workflows
- Apply RFC 2119 constraints (MUST, SHOULD, MAY)
- Validate SOP format and structure
- Convert workflows into reusable templates
- Ensure SOPs work across AI systems (Claude, Kiro, Cursor, etc.)
Core Concepts
What is an Agent SOP?
An Agent SOP is a standardized markdown file (.sop.md) that defines:
- Clear objectives with detailed overviews
- Parameterized inputs for flexible reuse
- Step-by-step instructions with RFC 2119 constraints
- Examples and troubleshooting for reliable execution
- Multi-modal distribution (MCP tools, Agent Skills, Python modules)
Key Features
RFC 2119 Constraints: Use standardized keywords (MUST, SHOULD, MAY) to provide precise control over agent behavior without rigid scripting.
Parameterization: Accept parameters that customize behavior for different projects, teams, or requirements.
Resumability: Document progress as agents work, making it easy to understand and resume if interrupted.
Creating Agent SOPs
File Location
You MUST check for an agent-sops/ directory in the current working directory:
- If
agent-sops/exists, You MUST write the SOP file there - If
agent-sops/does not exist, You MAY write the SOP in the current directory or ask the user where to save it
File Naming
You MUST follow these naming conventions:
- Use
.sop.mdfile extension - Use kebab-case for filenames (e.g.,
code-assist.sop.md,idea-honing.sop.md) - Choose descriptive names that indicate the SOP's purpose
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 406 lines · 41 tokens per session scan A 5fcf4bad72fd
agent-sop-author is a skill published in the GitHub repository strands-agents/agent-sop (1,142 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 3,020 once invoked, about $0.0002 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 skills, from other repositories
workflowhub
Use when the user wants OpenClaw or Codex to remember their way of working as reusable SOPs, workflows, queues, or "how I do things". Best for repeated multi-step tasks where the agent should proactively check saved workflows before starting, ask whether to reuse an existing SOP when there is a strong match, and ask…
analytics-funnel-attribution
Track acquisition and retention funnels for skill usage and workflow completion.
ai-llm-runtime-integration
Integrate runtime LLM orchestration for NPC and mission generation with guardrails.
analytics-privacy-anonymization
Anonymize analytics data to protect player privacy.
analytics-event-tracking
Track custom game events for player behavior analysis.
advanced-architecture-patterns
Design and implement advanced system architectures.