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 mfwarren/entrepreneur-claude-skills --skill sop-buildergit clone --depth 1 https://github.com/mfwarren/entrepreneur-claude-skillsWrote 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/mfwarren/entrepreneur-claude-skills/sop-builder)<a href="https://agentmods.dev/skills/mfwarren/entrepreneur-claude-skills/sop-builder"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/sop-builder/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/mfwarren/entrepreneur-claude-skills/sop-builder"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/sop-builder.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.00003 | $0.00817 |
| Opus 5.5 | $0.00001 | $0.00327 |
| Sonnet 5.5 | $0.00001 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
sop-builder 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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOP Builder
Create clear, repeatable standard operating procedures for any business process. Turn tribal knowledge into documentation anyone can follow.
Purpose
SOPs are the foundation of a scalable business. If a process lives in one person's head, it's a liability. This skill extracts, structures, and documents any business process into a format that a new hire could follow on day one.
Workflow
Step 1: Identify the Process
Ask the user:
- What process do you want to document?
- Who currently does this? (role, not person)
- How often does it happen? (daily, weekly, per-event)
- What triggers it? (customer request, scheduled, event-based)
- What does "done" look like?
Step 2: Extract the Steps
Walk through the process step by step:
- Ask "What happens first?"
- For each step: "Then what?" and "What could go wrong here?"
- Identify decision points: "If X, do Y. If not, do Z."
- Note tools, logins, or systems used at each step
- Capture time estimates per step
Step 3: Structure the SOP
# [Process Name] — Standard Operating Procedure
**Owner:** [Role]
**Frequency:** [How often]
**Trigger:** [What starts this process]
**Estimated Time:** [X minutes/hours]
**Last Updated:** [Date]
## Prerequisites
- [ ] [Access/tool/permission needed]
- [ ] [Information needed before starting]
## Steps
### 1. [Step Name]
**Action:** [What to do]
**Tool:** [System/app used]
**Notes:** [Tips, common mistakes, edge cases]
### 2. [Step Name]
...
## Decision Points
### If [condition]:
→ Do [action A]
### If [other condition]:
→ Do [action B]
## Quality Checklist
- [ ] [Verification step 1]
- [ ] [Verification step 2]
- [ ] [Verification step 3]
## Troubleshooting
| Problem | Cause | Solution |
|---------|-------|----------|
| [Issue] | [Why] | [Fix] |
## Escalation
If [condition], contact [role/person] via [channel].
Step 4: Add Context
For each step, include:
- Why this step matters (not just what to do)
- Screenshots or examples (suggest where the user should add them)
- Common mistakes to avoid
- Time estimate for that step
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.
- 1mo ago First seen · 126 lines · 3 tokens per session scan A 8f835ab69125
sop-builder is a skill published in the GitHub repository mfwarren/entrepreneur-claude-skills (83 stars, last pushed 8mo ago), licensed MIT. It adds 3 tokens to every session and 817 once invoked, about $0.0000 per session on Opus 5.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
mm-init-project
A project setup workflow that creates a shared project record in Markdown files, including a passport, dashboard, handoff notes, and instructions for Claude.ai. Obsidian is a note-taking app that can store these files as a connected project vault.
mm-projects
A read-only overview of all registered projects stored in Obsidian notes. It shows each project's status, type, current GSD phase, recent activity, and number of open questions.
kanban-markdown
Create, read, update, move, and manage kanban board feature files backed by markdown with YAML frontmatter. Use when working with kanban boards, task/feature tracking, .devtool/features/ directories, feature files with status/priority frontmatter, or any project management tasks involving markdown-based kanban…
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
factory-collect
Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.