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-intake-and-scopegit 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-intake-and-scope)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-process-intake-and-scope"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-process-intake-and-scope/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-process-intake-and-scope"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-process-intake-and-scope.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.00125 | $0.01957 |
| Opus 5 | $0.00063 | $0.00979 |
| Sonnet 5 | $0.00025 | $0.00391 |
| Haiku 4.5 | $0.00013 | $0.00196 |
Grade A, and why
okhp3-process-intake-and-scope 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-process-intake-and-scope
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Purpose
This skill guides structured process intake and scope definition using BABOK v3-aligned elicitation techniques. It produces:
- Process Intake Record (PIR) — structured YAML with trigger, actors, inputs, outputs, steps, exceptions, business rules, systems, and controls
- Scope Statement — concise prose defining process boundaries, exclusions, and success criteria
The PIR is the foundational input consumed by every downstream skill in the BP-SKILL suite.
When to use this skill
- User wants to document a process they describe in natural language, bullet points, or prose
- User says "help me scope this," "let's map this process," or "define the boundaries"
- You need a structured PIR before calling
stakeholder-and-role-mappingorprocess-narrative-authoring - User wants to capture business rules, exception paths, or system touchpoints for a workflow
When NOT to use this skill
- A validated PIR with
ready_for_narrative: truealready exists — proceed toprocess-narrative-authoring - User wants a diagram without prior discovery — use
visual-process-modelingwith their description - Do not invent process details the user has not provided — record gaps as
open_questions
Intake Workflow
Execute the following stages in order. Conduct a natural conversation — do not present these as a checklist. Load references/pir-schema.md for full field reference.
Stage 0 — Orientation
Ask: "Before we start, can you give me one sentence: what does this process produce or accomplish?"
Record as process_name. If vague, probe: "Who benefits when this process runs correctly? What do they get?"
Stage 1 — Trigger
Ask: "What causes this process to start — a person doing something, a scheduled date, an incoming message, or a system event?"
Classify trigger.event_type:
- Person acts →
manual - Date/frequency →
scheduled - Message/request/email →
message - System condition →
system
What ships with it
9 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.
- assets/fixtures/intake-purchase-approval.yaml 3.4 KB
- package.json 175 B
- README.md 1.2 KB
- references/pir-schema.md 3.0 KB
- scripts/generate-pir.mjs 3.0 KB runs code
- scripts/parse-yaml-minimal.mjs 4.6 KB runs code
- scripts/score-intake-completeness.mjs 9.9 KB runs code
- scripts/validate-pir.mjs 12 KB runs code
- tests/validate-skill.test.mjs 3.5 KB runs code
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 · 199 lines · 125 tokens per session scan A 28b950fb9192
okhp3-process-intake-and-scope is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,957 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
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.
pm-risk
A structured process for identifying, rating, responding to, and monitoring project risks before important delivery points or launch.
pm-user-story
A workflow for turning product requirements into user stories: short statements of what a user wants and why, with acceptance criteria for checking the result.