Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jamesgray-ai/handsonai-pluginsnpx agentmods add skills/jamesgray-ai/handsonai-plugins/writing-process-guidesWrote 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-process-guides)<a href="https://agentmods.dev/skills/jamesgray-ai/handsonai-plugins/writing-process-guides"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/writing-process-guides/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/jamesgray-ai/handsonai-plugins/writing-process-guides"><img src="https://agentmods.dev/badge/skills/jamesgray-ai/handsonai-plugins/writing-process-guides.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.00084 | $0.01388 |
| Opus 5 | $0.00042 | $0.00694 |
| Sonnet 5 | $0.00017 | $0.00278 |
| Haiku 4.5 | $0.00008 | $0.00139 |
Grade A, and why
writing-process-guides 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 9d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Business Process Guides
Write comprehensive Business Process Guide documentation and save as markdown files. The guide file is the business process's AI Registry record — the generated REGISTRY.md groups workflows under processes using the guide's frontmatter, and the guide's path is set as guide: frontmatter on the Process node itself. External trackers are out of scope. Process guides explain the strategic context and rhythm of a complete business process, while individual workflow SOPs handle the tactical execution details.
Process Guide vs Workflow SOP
| Aspect | Process Guide | Workflow SOP |
|---|---|---|
| Level | Strategic | Tactical |
| Scope | Multiple workflows | Single workflow |
| Answers | When/Why/What order | How (step-by-step) |
| Audience | Decision-maker | Executor |
| Length | 1-2 pages | Detailed steps |
Process
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. In addition, this skill's primary record is the Process node itself: setguide:frontmatter onregistry/processes/<slug>.mdpointing at the guide file.
- Load process context — Determine how the user is arriving:
- From the AI Registry (primary path): Read the Process node's (
registry/processes/<slug>.md) curated# Workflowslist for its component workflows. Read each linked Workflow node for trigger and status, plus its Workflow Requirements, Design Spec, and SOP where they exist (via the node's# Artifactslinks). - From conversation: If no artifacts exist, gather process details interactively (name, component workflows, sequence, triggers).
- From the AI Registry (primary path): Read the Process node's (
- Gather strategic context from user — frequency, timing, decision points between workflows, success criteria
- Write Process Guide using template
- Write process guide markdown file to user's repo with YAML frontmatter. Default path:
process-guides/<name>.md. Ask the user where process guides live if their project has a different convention. - Create or update
REGISTRY.mdat the workspace root so the process appears with its workflows — follow theindexing-registryprocedure if available, otherwise update its tables directly from the guide and registry data (skip only if the root isn't writable, and say so — never silently). Then invoke theindexing-registryskill for a maintenance pass (best-effort — a failed refresh never fails this step).
What ships with it
2 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.
- 9d ago First seen · 103 lines · 84 tokens per session scan A dc60e9bc43b5
writing-process-guides is a skill published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed 28d ago), licensed MIT. It adds 84 tokens to every session and 1,388 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-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…