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-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-process-capture)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-process-capture"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-process-capture.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.00128 | $0.00850 |
| Opus 5 | $0.00064 | $0.00425 |
| Sonnet 5 | $0.00026 | $0.00170 |
| Haiku 4.5 | $0.00013 | $0.00085 |
Grade A, and why
okhp3-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 7d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-process-capture
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
The intake mechanism. Turns "I just did this for the third time" into a structured artifact, not a lost observation.
Process
-
Extract the pattern. From the current conversation (or a description the user gives), identify: what was the task, what tools/skills were used, what was the input, what was the output, were there corrections or judgment calls along the way that would need to be encoded as instructions.
-
Assess readiness. Has this pattern stabilized enough to write down, or is this still "developing taste" (per the original delegation-contract framing — genuinely novel judgment calls each time means it's not a skill yet)?
- Not ready -> write a
docs/BACKLOG.mdentry (date, task, times observed, candidate family, status: captured). Stop here. - Ready -> continue to step 3.
- Not ready -> write a
-
Determine target family. Does this fit an existing family (
mermaid/,social-posting/, or this repo's ownprocess-capture/), or does it need a new top-level family? If new, note this explicitly — adding a new family directory is a bigger decision than adding a skill within one, and the user should confirm. -
Produce the skeleton. Frontmatter (
name, "pushy"descriptionper skill-creator's triggering guidance) + section-header outline matching the body's intended structure, with 1-2 sentence descriptions per section and pointers to reference files that will need authoring. Match the structure of existing skills in this repo (core+domain pattern for multi-skill families, single-skill pattern for self-contained ones). -
Update the index. Add the new skill's trigger row to root
AGENTS.md, even though the skeleton isn't fully authored yet — mark it in the "Planned" section if the body is still mostly TOC, move to "Active" once authored.
Handoff
A skeleton from this skill is a starting point for skill-creator (the Anthropic example skill, if available) for full authoring, testing, and description-optimization — this skill does intake and structure, not iteration and evals.
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.
- 7d ago First seen · 46 lines · 128 tokens per session scan A 49cd98e75a75
okhp3-process-capture is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session and 850 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.
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.
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.