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 danielrosehill/Claude-SOP-Writer-Plugin --skill import-to-sopgit clone --depth 1 https://github.com/danielrosehill/Claude-SOP-Writer-PluginWrote 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/danielrosehill/claude-sop-writer-plugin/import-to-sop)<a href="https://agentmods.dev/skills/danielrosehill/claude-sop-writer-plugin/import-to-sop"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-sop-writer-plugin/import-to-sop/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/danielrosehill/claude-sop-writer-plugin/import-to-sop"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-sop-writer-plugin/import-to-sop.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.00107 | $0.00605 |
| Opus 5 | $0.00053 | $0.00302 |
| Sonnet 5 | $0.00021 | $0.00121 |
| Haiku 4.5 | $0.00011 | $0.00060 |
Grade A, and why
import-to-sop 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 11d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
import-to-sop
Take raw source material and produce a structured SOP in the current project. This is where Claude does the actual restructuring work — extracting steps, warnings, materials, and contraindications from prose source material and slotting them into the template.
Inputs to gather
- Source — one of:
- URL (use WebFetch / fetch-and-convert MCP)
- Path to a local PDF (extract with
pdftotextor read directly) - Path to a local text/markdown file
- Pasted text in the conversation
- Template — same options as
new-sop(first-aid,emergency,household-procedure,troubleshooting-flow,recipe-method). If unclear, suggest based on source content. - Title — derive from source if not given; confirm with user.
- Output directory — default
sops/.
What to do
- Fetch / read the source material.
- Identify the structural elements relevant to the chosen template:
- Steps — ordered actions
- Warnings / contraindications — what NOT to do, when to stop, when to escalate
- Materials / equipment — what's needed
- Prerequisites — conditions that must hold before starting
- Decision points — branches in the procedure ("if X, then Y; otherwise Z")
- Escalation / when to call for help
- Map those into the template's section structure.
- Preserve attribution: include a
sourcefield in the SOP frontmatter pointing back to the original (URL or document title), so the user can verify the procedure later. - Flag anything ambiguous or missing in the source as
// TODO:comments inline in the Typst file — don't fabricate steps. - Write the file to
<output-dir>/<slug>.typ.
Important
- Never invent procedural steps that aren't supported by the source. If the source is incomplete, leave gaps and flag them.
- For first-aid and medical content especially, preserve the source's exact warnings verbatim where possible. Don't paraphrase a "call emergency services if X" instruction into something looser.
- Include a revision note at the top of the file indicating this was imported, the date, and the source.
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.
- 11d ago First seen · 41 lines · 107 tokens per session scan A 9d0ddd264b92
import-to-sop is a skill published in the GitHub repository danielrosehill/Claude-SOP-Writer-Plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 107 tokens to every session and 605 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…