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 OKHP3/skillz --skill okhp3-as-is-process-capturegit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/okhp3-as-is-process-capture)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-as-is-process-capture"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-as-is-process-capture/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/okhp3/skillz/okhp3-as-is-process-capture"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-as-is-process-capture.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.00114 | $0.01426 |
| Opus 5 | $0.00057 | $0.00713 |
| Sonnet 5 | $0.00023 | $0.00285 |
| Haiku 4.5 | $0.00011 | $0.00143 |
Grade A, and why
okhp3-as-is-process-capture 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 10d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-as-is-process-capture
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Purpose
Capture and normalise the current-state (as-is) process into a structured YAML artifact. The as-is record uses stable act-NNN step identifiers that persist across revisions, making gap analysis and change tracking tractable.
When to use this skill
- User describes how a process runs today and wants it documented before redesign
- You need a baseline artifact before running
process-gap-and-exception-analysis - PIR exists but steps lack stable IDs — normalise them with
scripts/assign-step-ids.mjs - User imports existing process notes, SOPs, or procedure documents for structuring
When NOT to use this skill
- No PIR exists — run
process-intake-and-scopefirst to establish scope and boundaries - User wants to design a future state only — skip to
future-state-and-change-strategy - Do not include aspirational or proposed changes in the as-is record
Capture Workflow
Step 1 — Import and triage
Identify the source: natural language description, bullet list, existing SOP document, or flowchart image. Determine if a PIR already exists. If not, run process-intake-and-scope first.
Step 2 — Extract and sequence steps
Parse all process steps in the order they occur. Each step must have:
- A single imperative action statement (IEEE 29148)
- An identified actor or role
- Entry criteria (what triggers this step)
- Exit criteria (what signals completion)
Step 3 — Assign stable IDs
Run scripts/assign-step-ids.mjs to assign act-001, act-002, … identifiers. IDs are:
- Sequential within each process
- Prefixed
act-for activities,gw-for gateways,evt-for events - Stable — once assigned, they do not change even if steps are reordered
Step 4 — Identify current-state gaps
Flag steps that are:
- Undocumented ("we just know to do it")
- Person-dependent ("only Alice knows this part")
- Inconsistently executed ("sometimes we skip this")
- Missing a named actor
What ships with it
6 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.
- 10d ago First seen · 142 lines · 114 tokens per session scan A 34210ee1cbcc
okhp3-as-is-process-capture is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 114 tokens to every session and 1,426 once invoked, about $0.0006 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
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
pm-aarrr
A post-launch product-growth workflow based on AARRR: acquiring users, activating them, retaining them, earning revenue, and gaining referrals.
pm-docs
A workflow for producing product documents such as PRDs, BRDs, and MRDs. These are structured documents describing what a product needs, its business case, and its market.
product-marketing-copywriter
A marketing-copy tool that analyzes audience problems and product benefits, then creates promotional headlines and body text. Marketing copy is writing intended to explain and promote a product.
pm-position
A guided process for defining a product’s market position, value, audience, competitive difference, business model, pricing, and revenue plan. The instructions are written mainly in Chinese.
pm-retro
A retrospective workflow for reviewing a finished agile iteration, recording what happened, and choosing improvements for the next cycle.