issue-triage

issue-triage is a skill for Claude Code, Codex from denoland/deno. It costs 47 tokens per session (1,855 once invoked), scanned C, original, MIT.

A guide for investigating Deno GitHub issues by reproducing bugs, classifying them, adding labels, and commenting with findings. Deno is a runtime for running JavaScript and TypeScript programs.

In plain words
What is it for?
Use it when given a Deno issue number or URL to assess whether it is a bug, feature request, question, duplicate, or invalid report, and to request missing information when necessary.
Why use it?
It provides a consistent triage process and identifies when an issue lacks the version, operating system, or reproduction details needed for investigation.

Skill for Claude CodeCodex

About the project

Deno is a runtime that executes JavaScript, TypeScript, and WebAssembly programs outside a browser. Developers use it for applications such as web servers, and the catalogue add-ons provide workflows and guidance for Deno projects.

denoland/deno · 108,370 stars · on GitHub · deno.com

Install

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.

agentmods
npx agentmods add skills/denoland/deno/issue-triage
Any agent
npx skills add denoland/deno --skill issue-triage
Clone the repo
git clone --depth 1 https://github.com/denoland/deno

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for issue-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/denoland/deno/issue-triage.svg)](https://agentmods.dev/skills/denoland/deno/issue-triage)
Your own site
<a href="https://agentmods.dev/skills/denoland/deno/issue-triage"><img src="https://agentmods.dev/badge/skills/denoland/deno/issue-triage.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,855 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01855
Opus 5 $0.00023 $0.00928
Sonnet 5 $0.00009 $0.00371
Haiku 4.5 $0.00005 $0.00186

Measured 6d ago against content hash 52756b70f45b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade C, and why

issue-triage scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$REPRO_DIR"
.claude/skills/issue-triage/SKILL.md · 228 lines

How it starts

The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deno Issue Triage

Triage issue $ARGUMENTS on the denoland/deno repository.

Step 1: Read the issue

gh issue view $ARGUMENTS --repo denoland/deno --json number,title,body,author,labels,state,comments,createdAt,url

Step 2: Classify the issue

Determine what kind of issue this is:

  • Bug report — something isn't working as expected
  • Feature request / suggestion — a new capability or enhancement
  • Question — a usage question, not a bug
  • Duplicate — already reported (search closed and open issues with gh issue list --search "keywords" --state all)
  • Invalid — not actionable, not a Deno issue, or insufficient info

If the issue is clearly a question, duplicate, or invalid, skip reproduction and go straight to Step 5.

Step 3: Check for missing information

A valid bug report needs:

  • Deno version (deno --version output)
  • Operating system
  • Reproduction steps or minimal reproduction code
  • Expected behavior vs actual behavior

If any of these are missing, label as needs info and comment asking the author to provide the missing details. Do not attempt reproduction without a clear repro case.

Step 4: Reproduce the bug

Only attempt reproduction for bug reports that have a clear repro case.

Setup

Prefer running reproductions inside a Docker container for isolation. Fall back to a local temp directory only if Docker is unavailable.

Docker (preferred):

# Run repro with latest canary
docker run --rm -v "$REPRO_DIR":/repro -w /repro denoland/deno:canary deno run repro.ts

# Run repro with a specific version (e.g., 2.1.4)
docker run --rm -v "$REPRO_DIR":/repro -w /repro denoland/deno:2.1.4 deno run repro.ts

Use docker run --rm so containers are cleaned up automatically. Mount the repro files via -v.

Local fallback (if Docker is not available):

REPRO_DIR=$(mktemp -d)
deno run "$REPRO_DIR/repro.ts"

Get Deno versions

Try to reproduce with both:

  1. The version from the issue (if specified) — to confirm the bug exists
  2. Latest canary — to check if it's already fixed

Read the full file on GitHub · 228 lines

Changes

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.

  1. 6d ago First seen · 228 lines · 47 tokens per session scan C 52756b70f45b

Subscribe to this mod's changes

issue-triage is a skill published in the GitHub repository denoland/deno (108,370 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,855 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.