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 shashankreddy509/claude-tdd-kit --skill bug-triagegit clone --depth 1 https://github.com/shashankreddy509/claude-tdd-kitWrote 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/shashankreddy509/claude-tdd-kit/bug-triage)<a href="https://agentmods.dev/skills/shashankreddy509/claude-tdd-kit/bug-triage"><img src="https://agentmods.dev/badge/skills/shashankreddy509/claude-tdd-kit/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/shashankreddy509/claude-tdd-kit/bug-triage"><img src="https://agentmods.dev/badge/skills/shashankreddy509/claude-tdd-kit/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.00163 | $0.02170 |
| Opus 5 | $0.00081 | $0.01085 |
| Sonnet 5 | $0.00033 | $0.00434 |
| Haiku 4.5 | $0.00016 | $0.00217 |
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 10d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Triage
The user invoked /bug-triage with: {{args}}
One job: take a Jira bug key and drive it to a root-cause verdict + fix-location, then write that result to an artifact a planner can consume. This is orchestration — it sequences a fixed workflow and DELEGATES (Jira fetch, the read-only Explore fan-out, the pre-existing check) rather than doing analysis it doesn't own. Keep the JUDGMENT here (classify, pick the real root cause, write the verdict); push the mechanics out to agents/skills.
It is hard-scoped:
- Read-only. Never transitions, comments, edits, or assigns the ticket. It only READS Jira.
- Never writes code. No fix, not even a fix plan. It stops at the verdict + the file:line where the fix belongs, and hands that to a planner via the artifact. (Producing a plan would make it straddle into planning — that's the consuming planner's job, gated by the user's plan-gate.)
- Stops at the artifact.
tasks/<TICKET>-triage.mdis the contract. The user runs/build(or the plugin's build command) separately when they choose — those detect the triage file and write a LEAN fix-plan from it.
Gate FIRST
ticket is a required argument. If it's missing or ambiguous, STOP and ask — do not guess a key.
Discover the project's Jira config (cloudId + key) from the project CLAUDE.md — scan it for a
line of the form Jira: cloudId=<uuid> key=<PROJECTKEY> and use those values;
never hardcode a cloudId. If not found, ask for the cloudId + key. Normalize the ticket to <KEY>-NNNN.
Steps
1. Fetch the ticket (delegate the live read)
Resolve the Jira MCP dialect first. Atlassian MCP servers differ per machine: one exposes
camelCase names (mcp__atlassian__getJiraIssue) with cloudId REQUIRED; another exposes snake_case
under a jira prefix and resolves the site internally, with no cloudId at all. If the
tdd-pipeline plugin is installed, follow its references/jira-mcp.md. Otherwise probe inline: try
the camelCase name via ToolSearch; if nothing resolves, search by keyword
(ToolSearch "+jira issue") and use what comes back. Never hardcode a tool name.
What ships with it
1 file 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.
- 10d ago First seen · 137 lines · 0 tokens per session scan A 32819936a174
bug-triage is a skill published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 17d ago), licensed MIT. It adds 163 tokens to every session and 2,170 once invoked, about $0.0008 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
mk:jira-analyst
Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring…
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.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
create-issue
Transitional alias — prefer /prflow:specs, which runs the same issue-drafting pipeline. Use when a rough user story, bug report, feature idea, piece of feedback, or an implementation plan should be recorded as a GitHub issue rather than built right now. This command name is retained so existing /prflow:create-issue…
bugherd-automation
Automate Bugherd tasks via Rube MCP (Composio). Always search tools first for current schemas.