Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/triage)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/triage"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/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/bdfinst/agentic-dev-team/triage"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/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.00080 | $0.01986 |
| Opus 5.5 | $0.00032 | $0.00794 |
| Sonnet 5.5 | $0.00016 | $0.00397 |
| Haiku 4.5 | $0.00008 | $0.00199 |
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 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Triage
Role: worker.
Investigate a bug hands-off, find root cause, and write a TDD fix plan to a
portable triage record at .dev-team-reports/triage/<slug>.md — no
issue-tracker dependency.
Worker constraints
- Investigate and record; do not fix the bug.
- Find root cause before recording; do not record on symptoms alone — and do
not record an unverified, unrelated finding as if it were the root cause;
use the
unconfirmedoutcome instead. - Be concise. The record is structured; chat is the
triage-record:line plus a one-line root-cause summary — not the full body.
Process
1. Capture the Problem
Get the bug description from the arguments or conversation. If no description is
given, ask EXACTLY one question: What's the problem you're seeing? and stop.
If a description is given, ask nothing — start investigating immediately.
Scoped exception: if the description signals a cross-service or
intermittent symptom (it names multiple repos/services, or uses language like
"intermittent", "sometimes", or "inconsistently"), ask ONE additional targeted
question before investigating: Do you have any of the following: logs, a sample request/response pair, trace/audit IDs, or a config/pipeline export?
This is a narrow exception for that signal only — the "ask nothing" rule above
still applies to every other description, and the no-description fallback
question above is unchanged.
Arguments: $ARGUMENTS
2. Investigate
Apply the systematic debugging protocol from skills/systematic-debugging/SKILL.md:
- Reproduce: Run the failing test or trigger the error
- Investigate: Trace data flow, check recent changes, find working reference code
- Root cause: Form and test a hypothesis
Use the Agent tool with subagent_type: "Explore" to deeply investigate the codebase:
related source files and dependencies, existing tests (covered vs missing),
recent changes to affected files (git log), error handling in the code path,
and similar patterns elsewhere that work correctly.
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 First seen · 212 lines · 80 tokens per session scan A ad5855cd5f28
triage is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 80 tokens to every session and 1,986 once invoked, about $0.0003 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-05.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
resolve-author-fix
Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.