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-case-techgit 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-tech)<a href="https://agentmods.dev/skills/enmanuelmag/agent-harness-kit/ahk-use-case-tech"><img src="https://agentmods.dev/badge/skills/enmanuelmag/agent-harness-kit/ahk-use-case-tech/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-tech"><img src="https://agentmods.dev/badge/skills/enmanuelmag/agent-harness-kit/ahk-use-case-tech.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00450 |
| Opus 5 | $0.00010 | $0.00225 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
ahk-use-case-tech 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 3d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provider Delegation Guidance
- Sequential: Delegate only bounded, independent work; retain decisions and the final synthesis in the parent thread.
- Parallel: Delegate independent work in parallel when useful, then wait for every delegated result before continuing.
- Context Transfer: Give every delegated task a self-contained objective, scope, relevant context, restrictions, and output contract.
- Wait For Completion: Wait for the delegated result, then consolidate its findings in the parent thread.
- Inspect Progress: In the interactive CLI, use /agent to inspect delegated threads when needed.
Entry gate
Start by locating the requested use-case with specs.list and reading it with specs.get. Stop if it is not an approved use-case; help resolve it with ahk-use-cases first.
Read the technical workflow before analysis and the technical template before saving.
Investigation
Inspect the relevant codebase before proposing technical work. For every library, framework, SDK, API, CLI, cloud service, version, compatibility, configuration, or migration question: identify installed versions from manifests and lockfiles, query Context7 and the Mintlify documentation index when available, then use primary documentation for gaps. Record compatibility, upgrade need, new dependency need, and evidence. Do not treat an unverified assumption as a decision.
Proposal and persistence
Define affected boundaries, contracts and data flow, alternatives and rationale, compatibility findings, dependencies, rollout or migration, risks, validation, and a phased implementation plan. Link related specifications with specs.link; use depends-on, extends, supersedes, conflicts-with, or informs precisely.
Present the technical proposal for user approval before writing it. Once approved, create or update a technical specification through structured MCP tools with sourceSpec pointing to the approved use-case, then run specs.validate. A technical spec that is needs-reconciliation must not be used as an implementation plan until reconciled and approved again.
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.
- 3d ago Changed · +9 lines 681830c51f84
- 4d ago First seen · 21 lines · 21 tokens per session scan A 5497a3ea04a8
ahk-use-case-tech is a skill published in the GitHub repository enmanuelmag/agent-harness-kit (180 stars, last pushed 2d ago), licensed Apache-2.0. It adds 21 tokens to every session and 450 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
OpenCode
Frames OpenCode as an operator-controlled coding lane for bounded implementation or review work inside a real repository.
opencode
Use when working with a model-agnostic terminal AI coding agent that uses opencode.json for declarative configuration — MCP servers, custom commands, agent routing, skills. OpenCode: configuration-as-code terminal AI coding agent with multi-model support.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
nano-banana-pro-openrouter
Deterministic OpenRouter image generation adapter for Nano Banana Pro / Gemini image models. Use as skillexec when a meta-skill needs local image files and structured IMAGEREADY records without spawning an LLM agent.
skill-creator-linter
Internal tool (not user-invocable). Called by meta-skill-creator as a DAG step (kind: agent) to lint a candidate meta-skill SKILL.md against G1 (parse + reference check + xmlescape grep + structural lint) and G2 (scheduler dry-run with stub executors). Deterministic, sub-second, no LLM. Returns JSON diagnostics.
paper-abstract-author
Write the abstract after the paper body has been revised, using the final claims and evidence.