Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSmokeDev/taskchad-os/master/.claude/skills/sop-creator/SKILL.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/sop-creator)<a href="https://agentmods.dev/skills/thesmokedev/taskchad-os/sop-creator"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/sop-creator/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/thesmokedev/taskchad-os/sop-creator"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/sop-creator.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.00076 | $0.01507 |
| Opus 5 | $0.00038 | $0.00754 |
| Sonnet 5 | $0.00015 | $0.00301 |
| Haiku 4.5 | $0.00008 | $0.00151 |
Grade A, and why
sop-creator 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 6d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOP & Runbook Creator
Create practical documentation that people actually follow.
Philosophy
Nobody reads 50-page docs. Make it scannable, actionable, and impossible to misunderstand.
Core principles:
- Scannable - Headers, bullets, tables. No walls of text.
- Actionable - Every step is something you DO, not something you "consider"
- Specific - Numbers, names, thresholds. No "as needed" or "when appropriate"
- Testable - Clear success criteria. How do you know it worked?
- Maintained - Owner, last updated, review schedule
SOP Categories
Pick the right format for your use case:
Tech/Engineering
| Type | When to Use |
|---|---|
| Runbook | Emergency response, incidents, on-call |
| Deployment Playbook | Releases, migrations, maintenance |
| Troubleshooting Guide | Debugging, diagnosis trees |
| How-To Guide | One-off setup, configuration |
| ADR | Architecture decisions |
Operations/Business
| Type | When to Use |
|---|---|
| Process SOP | Repeatable business workflows |
| Checklist | Quality control, verification |
| Decision Tree | Complex if/then scenarios |
| Handoff Doc | Role transitions, shift changes |
Content/Creative
| Type | When to Use |
|---|---|
| Production Workflow | Content creation pipelines |
| Review Process | Approval workflows |
| Publishing Checklist | Pre-launch verification |
General
| Type | When to Use |
|---|---|
| Standard SOP | Any repeatable process |
| Quick Reference | Condensed version of longer SOP |
| Onboarding Guide | New person ramping up |
Universal Structure
Every SOP needs at minimum:
# [What This Does]
> **TL;DR:** One sentence - what, when, who.
## Definition of Done
This is complete when:
- [ ] [Primary outcome]
- [ ] [Verification step]
- [ ] [Any handoff/notification]
## When to Use This
[Trigger conditions]
## Prerequisites
[What you need before starting]
## The Process
[Numbered steps - the actual work]
## Verify Completion
[Return to Definition of Done, confirm all checked]
## When Things Go Wrong
[Common issues and fixes]
## Questions?
[Who to contact]
What ships with it
7 files 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.
- 6d ago First seen · 217 lines · 76 tokens per session scan A b7e2b7979a1a
sop-creator is a skill published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 1,507 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-workflows
Workflow automation: native step types, multi-step workflows, parallel/matrix/wait/container/emulator steps, when: conditions (CEL), require/assert preconditions, output steps, retries, dependencies, and cross-component orchestration.
atmos-imports
Atmos imports: local and remote stack imports, go-getter schemes, templated imports, import context, remote imports vs component source/vendoring, and private GitHub imports through github/sts.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…