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 matheusPavaneli/workbench --skill triage-taskgit clone --depth 1 https://github.com/matheusPavaneli/workbenchWrote 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/matheuspavaneli/workbench/triage-task)<a href="https://agentmods.dev/skills/matheuspavaneli/workbench/triage-task"><img src="https://agentmods.dev/badge/skills/matheuspavaneli/workbench/triage-task/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/matheuspavaneli/workbench/triage-task"><img src="https://agentmods.dev/badge/skills/matheuspavaneli/workbench/triage-task.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.00051 | $0.00848 |
| Opus 5.5 | $0.00020 | $0.00339 |
| Sonnet 5.5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
triage-task 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 20d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
triage-task
All tracker access goes through one command. Never construct JQL, WIQL, URLs or field lists — the provider builds them from the resolved context.
wb <args> # wb not on PATH: python <this skill's directory>/../../lib/wb.py <args>
Steps
-
Key given? Go straight to step 2:
start <KEY>resumes as well as starts. With no key,statuslists every ticket with work in flight and the one command that moves each on. -
No key given —
task list. Four columns, newest first. Show them and ask which one, unless the request already names one.No tracker in this repo?
task new "title" --type bug|feature|chore|supportrecords it in the local backlog and everything downstream works unchanged. Only local contexts accept it;wbsays so if the repo has a real tracker. -
Pick it up —
start <KEY>. Reads the ticket into.workflow/<KEY>/triage.jsonand prints its text, puts the checkout on the ticket's branch, and ends with the route and the one next command. Rerun it any time: it is a no-op that says where the ticket stands. To read without branching, or deeper, usetask get <KEY>— depth 1 by default: the task, plus one line per linked item.- Use
--depth 0when the ticket is self-contained and links do not matter. - Use
--depth 2only when a blocker or a parent decides the approach. It fetches bodies for blocking and hierarchy links, never forrelates.
Light path (the route says so): no plan, no other skill, no
status. Make the change and a test that covers it, thenfinish <KEY> -m "<type>: <summary>" --commit. It runs the suite, the regression check and the message check itself, so do not run them first; on a pass it commits exactly the checked files. If it says the work outgrew the path, continue withplan-change. - Use
-
Go deeper only where it pays — the
_expandlist names what exists but was not included. Pass a handle back verbatim:task get <KEY> --expand comments:all. Do not compose handles; anything not in_expandis rejected.
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.
- 20d ago Changed 0b1746b2b6f9
- 21d ago Changed · +12 lines d7181c4dc004
- 1mo ago First seen · 58 lines · 51 tokens per session scan A 2677ab766405
triage-task is a skill published in the GitHub repository matheusPavaneli/workbench (1 stars, last pushed 20d ago), licensed MIT. It adds 51 tokens to every session and 848 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-08-31.
Other skills, from other repositories
dev-kit-setup
First-use bootstrap for the dev kit. Detects the team's issue tracker, discovers what it can via MCP/CLI, asks only what cannot be discovered, and persists the result to .claude/dev-kit.json in the consuming repo. Use when that file is missing, when the user asks to set up or reconfigure the kit, or when issue-fetch…
plan-backlog
Turn an idea or description (in any format) into a well-formed backlog — epics, user stories with acceptance criteria, sub-tasks — and create it in the team's tracker after approval. Elaborates progressively (guided, the default) or in one shot (--quick). Supports Jira, Linear, GitHub Issues, and Azure DevOps via…
issue-fetch
Fetch a work item (summary, status, description, acceptance criteria, comments) from the team's issue tracker and display a clean summary. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use whenever a prompt contains an issue reference (e.g. PROJ-1234, ENG-42.
issue-update
Update the work item after delivery - comment the PR link and a product-facing summary, and transition it to the team's review status. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use right after a PR is created for a story, or when the user asks to update/move a ticket.
plan-definition
Turn a spark (an idea, even a one-liner, in any format) into a clear product definition through a guided, Socratic discovery phase — frame the problem (users, outcome, metrics, constraints, non-goals), explore 2–4 directions with trade-offs, and produce an approved definition that then feeds plan-backlog. Facilitate…
work-story
Work a user story end to end — fetch the ticket, plan (with approval), implement, verify the applicable gates, self-review, open the PR, and update the tracker. Use when given an issue key like PROJ-1234, ENG-42, or.