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-skill-promotiongit 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-skill-promotion)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-skill-promotion"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-skill-promotion/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-skill-promotion"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-skill-promotion.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.00083 | $0.02353 |
| Opus 5 | $0.00042 | $0.01177 |
| Sonnet 5 | $0.00017 | $0.00471 |
| Haiku 4.5 | $0.00008 | $0.00235 |
Grade A, and why
okhp3-skill-promotion 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-skill-promotion
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Outcome
Turn a useful project-local skill into a traceable, portable promotion package without creating competing editable sources or silently publishing project context.
The three-surface model
Treat a skill as one identified package with staged representations:
| Surface | Path | Authority while incubating | Purpose |
|---|---|---|---|
| Runtime source | .agents/skills/<name>/ |
Originating project | Immediately usable local skill |
| Publication mirror | skills/<name>/ |
Generated from runtime source | Portable candidate for review and sharing |
| Canonical distribution | <family>/<name>/ in OKHP3/skillz |
Accepted distribution package | Installable public skill |
The runtime source is the editable source while the skill is being developed. The publication mirror is managed output, not a second authoring location. After canonical promotion, the portable core is maintained through an explicit, reviewed update from the canonical package. Project-specific adapters may remain different when the difference is documented.
Scope boundary
| In scope | Out of scope |
|---|---|
| Compare candidate copies and select a source using evidence | Choosing a source by timestamp, line count, or version alone |
Create or verify a local skills/<name>/ mirror |
Blindly overwriting a divergent mirror |
| Produce a provenance and promotion manifest | Uploading, committing, pushing, or opening a PR without authorization |
| Route to Foundry, catalog, validation, and repository guidance | Treating a passing structural check as proof of task quality |
| Preserve local context and identify public-safety blockers | Guessing whether private material is safe to publish |
Required inputs
Collect these before writing:
- The project root and the candidate package path.
- The intended mirror path, normally
skills/<name>/. - The proposed canonical
skillzfamily and package path, if known. - Repository guidance, relevant
AGENTS.mdfiles, and current Git status. - The package's license, author, dependencies, intended clients, and known project-specific context.
- Existing evaluations, validation reports, or failure examples.
What ships with it
8 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/promotion-manifest-template.json 1.4 KB
- benchmarks/equilibrium-review-2026-08-02.json 2.3 KB
- benchmarks/structural-integrity-2026-08-02.json 1.6 KB
- benchmarks/sync-verification-2026-08-02.json 2.0 KB
- evals/evals.json 5.5 KB
- references/promotion-manifest.md 1.9 KB
- scripts/sync_skill_mirror.py 6.6 KB runs code
- tests/test_sync_skill_mirror.py 4.0 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.
- 10d ago First seen · 255 lines · 83 tokens per session scan A dae6a325280f
okhp3-skill-promotion is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 2,353 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
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.