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 akougkas/wtf-p --skill wtfp-deliver-researchgit clone --depth 1 https://github.com/akougkas/wtf-pWrote 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/akougkas/wtf-p/wtfp-deliver-research)<a href="https://agentmods.dev/skills/akougkas/wtf-p/wtfp-deliver-research"><img src="https://agentmods.dev/badge/skills/akougkas/wtf-p/wtfp-deliver-research/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/akougkas/wtf-p/wtfp-deliver-research"><img src="https://agentmods.dev/badge/skills/akougkas/wtf-p/wtfp-deliver-research.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.00072 | $0.00531 |
| Opus 5 | $0.00036 | $0.00266 |
| Sonnet 5 | $0.00014 | $0.00106 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
wtfp-deliver-research 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 12d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliver WTF-P Research
Create reviewable delivery artifacts without overstating manuscript readiness.
Select the action
- Use
export-latexto convert ordered manuscript sections and bibliography data into a typesetting project. - Use
submit-milestoneto archive an immutable named research snapshot. - Use
create-slidesto turn the argument into a timed presentation. - Use
create-posterto turn the argument into a visual, non-linear research summary.
Read references/actions.md for the selected action before generating or archiving output.
Apply the delivery contract
- Resolve
project://manifest,project://structure/outline, section records, manuscript artifacts, verified source/evidence records, validations, figures, tables, and known gaps. - Ask for missing delivery constraints such as template, format, duration, dimensions, audience, authorship, and milestone label.
- Preserve claims, citations, equations, labels, captions, accessibility text, and asset provenance during transformation.
- Generate into explicit project-owned output paths. Never overwrite source manuscript files as part of a format conversion.
- Validate every generated artifact with the strongest available local checker and distinguish generation success from compilation or rendering success.
- Preview incomplete-section warnings, archive contents, record transitions, and every externally visible effect before applying them. Delivery actions do not execute version-control operations.
- Keep a manifest of outputs and unresolved manual steps.
- Report exact artifact paths, validation results, known limitations, and the next review or submission step.
Preserve delivery integrity
- Do not derive complete bibliography records from prose summaries; use verified bibliography data or flag missing records.
- Do not claim a PDF, slide deck, poster, tag, or archive exists until its output is verified.
- Make milestone labels path-safe and unique. Refuse traversal and accidental overwrite.
- Archive before resetting active planning state, then verify the archive independently.
- Keep delivery generation deterministic where inputs and template versions are fixed.
- Treat publishing, uploading, remote pushes, commits, and tags as separate explicit effects requiring their own declared action and approval.
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.
- 12d ago First seen · 40 lines · 72 tokens per session scan A 65953743b2e8
wtfp-deliver-research is a skill published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 13d ago), licensed MIT. It adds 72 tokens to every session and 531 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-30.
Other skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.