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 agentmods add skills/jl-cmd/claude-dev-env/issue-trackernpx skills add jl-cmd/claude-dev-env --skill issue-trackergit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWhat 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 | $0.00084 | $0.01159 |
| Opus 5 | $0.00042 | $0.00580 |
| Sonnet 5 | $0.00017 | $0.00232 |
| Haiku 4.5 | $0.00008 | $0.00116 |
Grade A, and why
issue-tracker 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker
User wants an issue action done. Here is how those actions work.
dedup -> do the work -> markers only -> numbers + URLs
Run every step the ask needs in one go (file, label, attach, refresh, and so on). The issue-tracker agent is the primary handler for one action per turn; this skill is the session path when the agent is unavailable or the ask spans several steps.
Prefer the same warm issue-tracker agent for follow-ups on the same issue or a related issue on the same epic. Spawn a new agent only for an unrelated work-stream or when the warm agent is gone.
Voice
Use the plain-brief output style (output-styles/plain-brief.md). End with the issue number(s) and URL(s) the caller must keep.
Gotchas
Append a bullet when an action fails in a new way.
- Use REST
.id, not display#N, to attach a sub-issue - operation-matrix. ghattach:-F sub_issue_id=<n>(typed int), never-f.- Status goes in markers, not comments - comments are cross-links only.
- Dedup open and closed; closed twin -> reopen vs file new, never silent refile.
- Edit only between markers - free-form epic edits break the children checklist.
- Auto-close is PR-body-first: a related-only UI link does not close the issue on merge.
The model
One epic issue owns a work-stream. Each unit of work is a native GitHub sub-issue under it. The epic checklist and every status block live inside marker pairs. Skeletons and refresh steps: reference/epic-and-sub-issue-model.md.
Labels
- Parent:
epic. - Sub-issue:
type: roadblock,type: task,type: bug, ortype: enhancement.
Create a missing label, then apply it. Label create is in the operation matrix.
Markers
- Status (any issue):
<!-- issue-tracker:status -->…<!-- /issue-tracker:status --> - Children checklist (epic only):
<!-- issue-tracker:children -->…<!-- /issue-tracker:children -->
Update path: read body -> replace only the text between the target pair -> write the full body back.
What ships with it
3 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.
- 2d ago First seen · 93 lines · 84 tokens per session scan A fd6246e7b7d3
issue-tracker is a skill published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 1,159 once invoked, about $0.0004 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
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.