sop-writer

sop-writer is a skill for Claude Code from Dokkabei97/forged-claude-code. It costs 36 tokens per session (1,034 once invoked), scanned A, original, MIT.

A skill for writing standard operating procedures, or SOPs: repeatable instructions that explain how a task should be done. It includes steps, checklists, decision points, and assigned responsibilities.

In plain words
What is it for?
Use it to document recurring tasks, create onboarding instructions, define prerequisites and ownership, or turn an informal process into a checklist.
Why use it?
It records routine work so the process does not depend on one person remembering every detail.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forged-claude-code plugin — 29 skills, 14 commands, 9 agents, 2 hooks shipped together

Good fit Use it to document recurring tasks, create onboarding instructions, define prerequisites and ownership, or turn an informal process into a checklist.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dokkabei97/forged-claude-code/sop-writer
Install

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.

Any agent
npx skills add Dokkabei97/forged-claude-code --skill sop-writer
Clone the repo
git clone --depth 1 https://github.com/Dokkabei97/forged-claude-code

Made for: Claude Code.

Or install forged-claude-code, the plugin that ships this one along with the rest of its 29 skills, 14 commands, 9 agents, 2 hooks.

Wrote 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.

agentmods badge for sop-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/sop-writer/github.svg)](https://agentmods.dev/skills/dokkabei97/forged-claude-code/sop-writer)
Your own site
<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/sop-writer"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/sop-writer/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.

agentmods 80×15 button for sop-writer

Your own site · 80×15
<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/sop-writer"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/sop-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,034 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01034
Opus 5 $0.00018 $0.00517
Sonnet 5 $0.00007 $0.00207
Haiku 4.5 $0.00004 $0.00103

Measured 8d ago against content hash 702a1cbd88bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sop-writer 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 8d 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.

skills/coo/sop-writer/SKILL.md · 165 lines

How it starts

The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SOP Writer - Standard Operating Procedure Generator

Overview

Documents "how we do things" so processes don't live in one person's head. If someone is on vacation and work stops, you need an SOP.


1. When to Apply

Trigger Behavior
Repetitive task needs documenting Full SOP creation
"SOP", "process document" Interactive SOP builder
New team member asks "how do I..." SOP generation prompt

2. SOP Template

# SOP: [Process Name]

| Field | Value |
|-------|-------|
| **Version** | 1.0 |
| **Last Updated** | YYYY-MM-DD |
| **Owner** | [Name/Role] |
| **Frequency** | [Daily/Weekly/Monthly/As needed] |
| **Estimated Time** | [N] minutes |

---

## Purpose
[1-2 sentences: why this process exists and what it achieves]

## Scope
- **Applies to**: [Who performs this]
- **When**: [What triggers this process]
- **Not covered**: [What this SOP doesn't address]

## Prerequisites
- [ ] [Access/tool/permission needed]
- [ ] [Knowledge/training required]

---

## Procedure

### Step 1: [Action Name]
**Who**: [Role]
**How**:
1. [Specific action with exact details]
2. [Include screenshots/links where helpful]
3. [Include expected result]

> ⚠️ **Caution**: [Common mistake to avoid]

### Step 2: [Action Name]
**Who**: [Role]
**How**:
1. [Specific action]
2. [Specific action]

**Decision Point:**
- If [condition A] → Go to Step 3
- If [condition B] → Go to Step 4
- If [unclear] → Escalate to [person/role]

### Step 3: [Action Name]
...

---

## Checklist Summary
- [ ] Step 1: [Brief description]
- [ ] Step 2: [Brief description]
- [ ] Step 3: [Brief description]
- [ ] Final verification: [What to check]

## Troubleshooting

| Problem | Likely Cause | Solution |
|---------|-------------|----------|
| [Problem 1] | [Cause] | [Fix] |
| [Problem 2] | [Cause] | [Fix] |

## Escalation
- **Level 1**: [Person/Role] — [contact method]
- **Level 2**: [Person/Role] — [contact method]

## Revision History
| Date | Version | Change | Author |
|------|---------|--------|--------|
| YYYY-MM-DD | 1.0 | Initial creation | [Name] |

Read the full file on GitHub · 165 lines

Changes

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.

  1. 8d ago First seen · 165 lines · 36 tokens per session scan A 702a1cbd88bd

Subscribe to this mod's changes

sop-writer is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,034 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-31.