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 2ykwang/agent-skills --skill django-ticket-triagegit clone --depth 1 https://github.com/2ykwang/agent-skillsWrote 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/2ykwang/agent-skills/django-ticket-triage)<a href="https://agentmods.dev/skills/2ykwang/agent-skills/django-ticket-triage"><img src="https://agentmods.dev/badge/skills/2ykwang/agent-skills/django-ticket-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/2ykwang/agent-skills/django-ticket-triage"><img src="https://agentmods.dev/badge/skills/2ykwang/agent-skills/django-ticket-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.00065 | $0.01471 |
| Opus 5 | $0.00032 | $0.00736 |
| Sonnet 5 | $0.00013 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
django-ticket-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 11d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Ticket Triage
Analyze a Django Trac ticket and recommend a triage stage.
Prerequisites:
python3(standard library only; no extra Python packages required)gh— GitHub CLI (install). Rungh auth loginto authenticate.- Django source code —
git clone https://github.com/django/django.gitin the working directory (for Step 5: source code analysis)
Before starting, verify python3 and gh are available. If gh is missing, show the install link and stop.
If django/ directory is missing, warn the user and skip Step 5 (source code browsing).
Arguments:
$ARGUMENTS: Trac ticket number (required, e.g.,36812,2750)
GitHub access: use the gh CLI for every GitHub lookup, not WebFetch. gh goes through the authenticated API and returns structured JSON; fetching a github.com URL returns rendered HTML that has to be scraped and breaks whenever the page layout changes.
- For commits:
gh api repos/<owner>/django/commits/<sha> - For PRs:
gh pr view <number> --repo django/djangoorgh api repos/django/django/pulls/<number> - See
references/gh-examples.mdfor more examples.
Note: ./scripts/ paths are relative to this SKILL.md file. Use the actual resolved path when executing.
Step 1: Fetch Ticket Details
python3 ./scripts/trac.py get $ARGUMENTS
Identify the following:
- Basic info: summary, reporter, owner, component, version
- Status: status, resolution, triage_stage, has_patch
- Keywords: Extract key terms from keywords field
- Ticket type: Bug report / Feature request / Documentation / Cleanup
- History: Review comments for previous discussions, related PRs, prior patch attempts
Step 2: Search for Duplicates and Related Tickets
2-1. Trac Search (at least 2-3 queries)
# Search by key keywords
python3 ./scripts/trac.py search "<key keywords>"
# Search by error message or class/function name
python3 ./scripts/trac.py search "<error message or class name>"
# Search by component + keyword combination
python3 ./scripts/trac.py search "<component> <keyword>"
What ships with it
7 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.
- 11d ago First seen · 183 lines · 65 tokens per session scan A 8b55fead793e
django-ticket-triage is a skill published in the GitHub repository 2ykwang/agent-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,471 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
resolve-plugins
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
debug-like-expert
Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
clawkeeper
Install, configure, verify, and debug the Clawkeeper watcher stack in this workspace. Use when a user asks to set up clawkeeper, initialize remote or local mode, enable clawkeeper-watcher, wire clawkeeper-bands, diagnose context-judge routing, inspect watcher logs, fix mode/config mismatches, or troubleshoot startup…
openclaw-parallels-smoke
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip…