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 jamesgray-ai/handsonai-plugins --skill writing-workflow-sopsgit clone --depth 1 https://github.com/jamesgray-ai/handsonai-pluginsWrote 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/jamesgray-ai/handsonai-plugins/writing-workflow-sops)<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/writing-workflow-sops"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/writing-workflow-sops.svg" alt="Measured on agentmods" 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.00105 | $0.02024 |
| Opus 5 | $0.00053 | $0.01012 |
| Sonnet 5 | $0.00021 | $0.00405 |
| Haiku 4.5 | $0.00011 | $0.00202 |
Grade A, and why
writing-workflow-sops 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Workflow SOPs
Write SOP documentation for workflows and save as markdown files, recording the SOP path in the workflow's Workflow node. External trackers are out of scope.
Registry entry: the workflow's registry entry is its Workflow concept node in the workspace's
registry/bundle — seeindexing-registry/references/registry-bundle.md(in this plugin) for resolution, write rules, and your fields. If the workspace has noregistry/SCHEMA.md, offer thescaffolding-registryskill first (it also migrates legacyworkflow.yamlworkspaces); do not write registry entries until the bundle exists.
Two-Axis Workflow Model
Every workflow has two independent characteristics that determine how its SOP should be written:
Axis 1 — Workflow Type (who does the work)
| Type | Definition |
|---|---|
| Manual | Human does all steps |
| Augmented | Human + AI collaborate |
| Automated | System does all steps, human monitors |
Axis 2 — Autonomy Level (where on the spectrum)
The AI Workflow Framework defines a single autonomy spectrum used at both the per-step and whole-workflow level:
Deterministic ———————— Guided ———————— Autonomous
(fixed path) (bounded decisions) (context-driven path)
For SOP template selection, the spectrum maps to a binary choice:
| Autonomy Level | SOP Weight |
|---|---|
| Deterministic | Full SOP — documents every step, branch, and decision point |
| Guided or Autonomous | Lightweight SOP — documents how to invoke, human checkpoints, inputs/outputs |
The key test: Can the executor change its path at runtime based on what it encounters? If yes (guided or autonomous) → lightweight SOP. If no (deterministic) → full SOP.
An agent can orchestrate at any autonomy level. An agent that runs a fixed script (step 1 → step 2 → step 3, no branching) is still deterministic and gets a full SOP. An agent that backtracks, re-invokes skills based on feedback, or adapts its sequence is guided or autonomous and gets a lightweight SOP.
What ships with it
1 file 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.
- 8d ago First seen · 144 lines · 105 tokens per session scan A c96f9beef295
writing-workflow-sops is a skill published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed 27d ago), licensed MIT. It adds 105 tokens to every session and 2,024 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…