import-to-sop

import-to-sop is a skill for Claude Code from danielrosehill/Claude-SOP-Writer-Plugin. It costs 107 tokens per session (605 once invoked), scanned A, original, MIT.

A tool for turning a URL, pasted text, PDF, or Markdown file into a structured Standard Operating Procedure, or SOP. It extracts procedural information and places it into a selected template.

In plain words
What is it for?
Use it to import existing instructions into first-aid, emergency, household, troubleshooting, or recipe templates and create a new Typst SOP file.
Why use it?
It saves you from manually reorganizing source material into sections such as steps, warnings, equipment, prerequisites, and decision points.

Skill for Claude Code

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

Part of the sop-writer plugin — 6 skills shipped together

Good fit Use it to import existing instructions into first-aid, emergency, household, troubleshooting, or recipe templates and create a new Typst SOP file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/danielrosehill/claude-sop-writer-plugin/import-to-sop
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 danielrosehill/Claude-SOP-Writer-Plugin --skill import-to-sop
Clone the repo
git clone --depth 1 https://github.com/danielrosehill/Claude-SOP-Writer-Plugin

Made for: Claude Code.

Or install sop-writer, the plugin that ships this one along with the rest of its 6 skills.

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 import-to-sop

README.md
[![agentmods](https://agentmods.dev/badge/skills/danielrosehill/claude-sop-writer-plugin/import-to-sop/github.svg)](https://agentmods.dev/skills/danielrosehill/claude-sop-writer-plugin/import-to-sop)
Your own site
<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.

agentmods 80×15 button for import-to-sop

Your own site · 80×15
<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>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 605 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.00107 $0.00605
Opus 5 $0.00053 $0.00302
Sonnet 5 $0.00021 $0.00121
Haiku 4.5 $0.00011 $0.00060

Measured 11d ago against content hash 9d0ddd264b92, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

skills/import-to-sop/SKILL.md · 41 lines

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

  1. Source — one of:
    • URL (use WebFetch / fetch-and-convert MCP)
    • Path to a local PDF (extract with pdftotext or read directly)
    • Path to a local text/markdown file
    • Pasted text in the conversation
  2. Template — same options as new-sop (first-aid, emergency, household-procedure, troubleshooting-flow, recipe-method). If unclear, suggest based on source content.
  3. Title — derive from source if not given; confirm with user.
  4. Output directory — default sops/.

What to do

  1. Fetch / read the source material.
  2. 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
  3. Map those into the template's section structure.
  4. Preserve attribution: include a source field in the SOP frontmatter pointing back to the original (URL or document title), so the user can verify the procedure later.
  5. Flag anything ambiguous or missing in the source as // TODO: comments inline in the Typst file — don't fabricate steps.
  6. 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.

Read the full file on GitHub · 41 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. 11d ago First seen · 41 lines · 107 tokens per session scan A 9d0ddd264b92

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens