Borrowing it
Nothing to install: this file belongs to sussdorff/timing-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sussdorff/timing-cli/main/.agents/skills/bug-triage/SKILL.mdgit clone --depth 1 https://github.com/sussdorff/timing-cliWrote 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/sussdorff/timing-cli/bug-triage)<a href="https://agentmods.dev/skills/sussdorff/timing-cli/bug-triage"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/bug-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/sussdorff/timing-cli/bug-triage"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/bug-triage.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.00021 | $0.00973 |
| Opus 5.5 | $0.00008 | $0.00389 |
| Sonnet 5.5 | $0.00004 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
bug-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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Triage
Systematic 4-phase workflow for diagnosing and fixing bugs. Prevents premature action by enforcing investigation before execution.
When to Use
Trigger on: bug, broken, kaputt, geht nicht, Fehler, regression, something is wrong, doesn't work, it's broken.
Do NOT use for: feature requests, performance improvements, or refactoring unrelated to a defect.
Phase 1: Reproduce
- Identify the exact reproduction steps from the bug report.
- Set up the environment as described (OS, version, dependencies).
- Execute the exact failing command or action.
- Observe the actual behavior vs. expected behavior.
- Confirm: does the bug occur consistently or intermittently?
If not reproducible: Ask only for missing evidence that changes the next investigation step. Continue safe independent code, existing-test and log inspection while awaiting it. Label hypotheses as unconfirmed; never invent a reproduction or report an unverified cause as established. Stop only work that depends on unavailable evidence or additional authorization.
Phase 2: Root Cause
Use relevant existing bug history, recent logs and cross-session memory when available. When the request refers to past work, search memory first. Missing integrations do not block local investigation; do not require unrelated history queries.
Step 4: Synthesize
From available evidence, form a hypothesis:
- What line/function is the defect in?
- What condition triggers it?
- Is it a regression (recently introduced)?
Phase 3: Fix
Rules:
- No cleanup, no refactoring, no opportunistic improvements.
- Touch only the files necessary to fix the confirmed root cause.
- Leave unrelated refactoring untouched and mention it in the report; do not file speculative follow-up issues.
- Use the existing issue. If a new work order is needed, author it inline through intake before implementation; touching multiple files does not justify a duplicate.
- A diagnosis request alone does not authorize a fix. For an authorized fix, the current implementation owner keeps source and repairs.
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.
- 1mo ago Changed f8797b0cdc49
- 1mo ago First seen · 121 lines · 21 tokens per session scan A b44cefbf7119
bug-triage is a skill published in the GitHub repository sussdorff/timing-cli (1 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 973 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-09-24.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.