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-triagegit 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-triage)<a href="https://agentmods.dev/skills/enmanuelmag/agent-harness-kit/ahk-triage"><img src="https://agentmods.dev/badge/skills/enmanuelmag/agent-harness-kit/ahk-triage/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-triage"><img src="https://agentmods.dev/badge/skills/enmanuelmag/agent-harness-kit/ahk-triage.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.00029 | $0.00461 |
| Opus 5 | $0.00015 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
ahk-triage 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 4d 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 — 54 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.
You are in lightweight triage mode.
If
$ARGUMENTSis empty, ask the user to describe the issue before doing anything else.
The issue: $ARGUMENTS
Rules
- NO MCP calls — no tasks., no actions.
- Run health.sh ONLY if the issue explicitly involves the build or test suite — not as a routine step
- NO builder, NO reviewer
- Create files ONLY if user explicitly asked to save the report
Process
-
Invoke Explorer as a subagent:
"Read-only diagnostic investigation — no MCP harness. Issue reported:
$ARGUMENTS. Investigate: which files are likely involved, what code paths produce this behavior, what assumptions might be violated, what state or environment conditions could trigger this. Return a detailed diagnostic analysis." -
Synthesize Explorer's findings into the REQUIRED output format below. Do not skip or reorder sections.
Required output format
TL;DR One paragraph. What is happening and the most likely cause.
Long Description Detailed analysis: what the code is doing, what it should do, where the divergence occurs.
Root Cause Analysis The causal chain: trigger → behavior → symptom. Name specific files, functions, and line numbers where relevant.
Possible Fixes Ordered most-to-least likely. Each fix must be a concrete actionable step naming specific files/functions.
Follow-up Questions (Omit this section entirely if investigation was sufficient. Include only genuine unknowns that would change the diagnosis.)
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.
- 4d ago Changed · +9 lines 7b88be13e1cc
- 11d ago First seen · 45 lines · 29 tokens per session scan A 11d89483bb58
ahk-triage is a skill published in the GitHub repository enmanuelmag/agent-harness-kit (181 stars, last pushed 3d ago), licensed Apache-2.0. It adds 29 tokens to every session and 461 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-08-30.
Other skills, from other repositories
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
code-task
PREFERRED way to change code in a REAL repository: fix a GitHub issue, fix a bug, add/implement a function or feature, or make any edit to a project the user names by a filesystem path (e.g. /tmp/foo, /code/bar) or a git URL. Clones the repo, runs an OpenSquilla agent on the host to make the change on a task branch…
stack-trace-js-probe
Internal helper for meta-stack-trace-investigator. Use when a JavaScript or TypeScript stack trace needs npm/node/tsc-specific checks, reproduction guidance, and patch targets.
stack-trace-generic-probe
Internal helper for meta-stack-trace-investigator. Use when a stack trace language is unknown and the workflow needs language-neutral failure-contract checks, reproducer guidance, and patch targets.