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 makifbaysal/tasktrooper --skill error-definitionsgit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/error-definitions)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/error-definitions"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/error-definitions/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/makifbaysal/tasktrooper/error-definitions"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/error-definitions.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.00053 | $0.00960 |
| Opus 5.5 | $0.00021 | $0.00384 |
| Sonnet 5.5 | $0.00011 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
error-definitions 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 9d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error definitions
An error definition says what one kind of runtime error means and what happens when it recurs. A person accepts or dismisses each one you propose, so every proposal has to stand on its own: a name a person recognises, a match they can read, a category and action they would have chosen, and a one-sentence rationale.
Category: what it is
| Category | It is | Usual action |
|---|---|---|
bug |
this code does the wrong thing (a nil dereference, an unhandled case, a wrong query) | task — one developer task per new group; incident if it breaks a core flow |
expected |
a designed outcome logged at error level (a cancelled checkout, a webhook for an unknown event, a cache miss logged loudly) | ignore, or none to keep it visible but labelled |
user_error |
input the code rejects correctly (validation, not found, unauthorised, rate limited) | ignore unless a sudden rise would mean an attack or a broken client — then alert with a threshold |
dependency |
a downstream service or API failing (timeouts, 5xx from a provider, a broker disconnect) | alert with a threshold: one timeout is noise, fifty in ten minutes is an outage |
infrastructure |
the platform itself (out of memory, disk full, DNS, the database refusing connections) | incident |
Read the code before you choose: the line that raises it, and what its callers do with it. A 404 the API returns on purpose is user_error; a 404 the service gets back from its own storage is a bug or a dependency.
Match: one kind of error, nothing else
Every field you set must hold.
fingerprint— exactly one group. Use it when the group is one specific failure and its message would match too much.message_regex— a family. Anchor on the words that never change (^payment provider timeout), escape what is literal (\(,\.), and never include an id, a timestamp, an amount or a host that varies between occurrences. Test it mentally against two different groups of the family.exception_type— the class or error type as printed before the first:; a bare name (TimeoutError) matches its qualified form.endpoint(POST /v1/charges,/v1/orders/*) andstatus(504) — when the message prints them, to tell the same exception on two routes apart.attributes— exactkey=valuepairs the message prints (tenant=acme), orsource/provider.
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.
- 9d ago First seen · 52 lines · 53 tokens per session scan A f2d8c1091fde
error-definitions is a skill published in the GitHub repository makifbaysal/tasktrooper (121 stars, last pushed 6d ago), licensed Apache-2.0. It adds 53 tokens to every session and 960 once invoked, about $0.0002 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-18.
Other skills, from other repositories
agent-performance-optimizer
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer.
agent-refinement
Agent skill for refinement - invoke with $agent-refinement.
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime →…
compute-sanitizer-diagnose-cuda-bugs
Detect and diagnose CUDA correctness bugs with NVIDIA Compute Sanitizer. Routes GPU memory errors, shared-memory data races, uninitialized-memory reads, and synchronization/barrier bugs to the right sub-tool (memcheck, racecheck, initcheck, synccheck) and explains how to build, run, and read the report. Use when…
dynamo-interconnect-check
Validate that a Dynamo deployment's NIXL/UCX/NCCL interconnect is ready for disaggregated serving over RDMA/NVLink. Use after recipe-runner brings a deployment up (especially disagg/multi-node) to confirm the KV transport is correct; use troubleshoot for diagnosing already-failed pods.