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 agentmods add skills/lwalden/aiagentminder/triagenpx skills add lwalden/AIAgentMinder --skill triagegit clone --depth 1 https://github.com/lwalden/AIAgentMinderWrote 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/lwalden/aiagentminder/triage)<a href="https://agentmods.dev/skills/lwalden/aiagentminder/triage"><img src="https://agentmods.dev/badge/skills/lwalden/aiagentminder/triage.svg" alt="Measured on agentmods" 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.00011 | $0.00901 |
| Opus 5 | $0.00005 | $0.00451 |
| Sonnet 5 | $0.00002 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aiagentminder:triage - Bug Triage
Systematically investigate a bug: reproduce it, diagnose the root cause, design a durable fix plan, and create a GitHub issue with the analysis. This is the structured start to debugging — complementing the debug checkpoint pattern (embedded in agent profiles) which handles the structured pause when a fix stalls.
Step 1: Capture the Problem
Get a clear bug description from the user (or from the skill argument). Clarify:
- Expected behavior — what should happen?
- Actual behavior — what happens instead?
- Steps to reproduce — how to trigger the bug
- Error output — error message, stack trace, or unexpected output
If any of these are unclear, ask before proceeding.
Step 2: Explore and Diagnose
Use the Agent tool to spawn an exploration subagent (subagent_type: "Explore"). The subagent's job:
- Trace the code path from the entry point (the user action or API call that triggers the bug) to the failure point.
- Read relevant source files, tests, and configuration — not the entire codebase.
- Report back:
- The code path involved
- Where the failure occurs
- A root cause hypothesis
Durability principle: Describe the root cause in terms of behaviors and contracts, not line numbers or internal variable names. The diagnosis should remain useful even if the code is refactored.
Step 3: Validate Root Cause
Attempt to confirm the root cause hypothesis:
- Run relevant tests to see if the failure is captured
- Reproduce the bug if possible (run the failing path)
- Check whether the hypothesis explains all symptoms
If the hypothesis doesn't hold after 2 iterations, trigger the debug checkpoint pattern: stop and present a structured checkpoint to the user with what's been tried, the current hypothesis, and what information would unblock progress.
Step 4: Design Fix Plan
Design the fix as a series of RED-GREEN test cycles:
- RED — a failing test that captures the bug behavior ("When X happens, the system should Y but currently does Z")
- GREEN — the minimal code change to make the test pass
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 · 112 lines · 11 tokens per session scan A 2d51aa497e6a
triage is a skill published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 901 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-31.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
joycraft-decide
Invoked at the design bookend by decompose's decision gate or the human directly — turn open questions into a decision dossier; every decision terminates clarified, backlogged, discarded, or assigned.
joycraft-bugfix
Structured bug fix workflow — triage, diagnose, discuss with user, write a focused spec, hand off for implementation.