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 enmanuelmag/agent-harness-kit --skill ahk-use-casegit clone --depth 1 https://github.com/enmanuelmag/agent-harness-kitWrote 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/enmanuelmag/agent-harness-kit/ahk-use-case)<a href="https://agentmods.dev/skills/enmanuelmag/agent-harness-kit/ahk-use-case"><img src="https://agentmods.dev/badge/skills/enmanuelmag/agent-harness-kit/ahk-use-case/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/enmanuelmag/agent-harness-kit/ahk-use-case"><img src="https://agentmods.dev/badge/skills/enmanuelmag/agent-harness-kit/ahk-use-case.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.00026 | $0.00260 |
| Opus 5.5 | $0.00010 | $0.00104 |
| Sonnet 5.5 | $0.00005 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
ahk-use-case 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 6d 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.
What it actually says
Start from the user's outcome, actor, and trigger. Ask exactly one decision question at a time. Research independent facts in the project with the available tools before asking the user to decide them.
Read the workflow and the template before saving.
Split the request when it contains independent actor-goal-result scenarios. Explain the proposed split and keep linked use cases separately reviewable. Do not choose implementation architecture, libraries, APIs, or a technical design.
Capture preconditions, main flow, alternatives, failures, business rules, boundaries, exclusions, observable outcome, and acceptance criteria. Persist a use-case draft with specs.create; real use cases are stored in docs/use-cases/. Save the first coherent draft before asking for explicit approval. Update it as the conversation refines it, validate after every write, and only transition it to approved after direct user approval.
An approved use case can be linked from a functional spec through sourceUseCases. Offer ahk-spec when the user wants scope and requirements derived from approved use cases.
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.
- 6d ago First seen · 15 lines · 26 tokens per session scan A eef1efdeb36f
ahk-use-case is a skill published in the GitHub repository enmanuelmag/agent-harness-kit (183 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 260 once invoked, about $0.0001 per session on Opus 5.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-10-10.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
company-hr
Run HR for a PenguinHarness organization — guarantee every employee has an enabled calendar event, hire and offboard employees (channels included), evaluate and improve them (with the default-rsi-toolkit plugin's agent-optimization skill), and keep the handbook's role conventions current.
company-mirror
Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.