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 alexmond/jhelm --skill issue-trackgit clone --depth 1 https://github.com/alexmond/jhelmWrote 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/alexmond/jhelm/issue-track)<a href="https://agentmods.dev/skills/alexmond/jhelm/issue-track"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/issue-track/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/alexmond/jhelm/issue-track"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/issue-track.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.00021 | $0.00344 |
| Opus 5.5 | $0.00008 | $0.00138 |
| Sonnet 5.5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
issue-track 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 1mo 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.
What it actually says
Track Issue Progress via Comments
Post a status update comment on GitHub issue #$ARGUMENTS.
Usage
The argument format is: <issue-number> <status> where status is one of:
start— Post a "Work started" commentplan— Post the implementation plan as a commentupdate <text>— Post a custom progress updatedone— Post a completion comment
Behavior
For start:
gh issue comment <number> --body "$(cat <<'EOF'
🔧 **Work started** on this issue.
Branch: `feature/<number>-<slug>` (will be created shortly)
EOF
)"
For plan:
Read /tmp/plan-<number>.md if it exists, and post it as a comment:
gh issue comment <number> --body "$(cat <<'EOF'
📋 **Implementation Plan**
<contents of /tmp/plan-<number>.md>
EOF
)"
For update <text>:
gh issue comment <number> --body "$(cat <<'EOF'
📝 **Progress Update**
<text>
EOF
)"
For done:
gh issue comment <number> --body "$(cat <<'EOF'
✅ **Implementation complete** — PR created and CI checks passing.
EOF
)"
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.
- 1mo ago First seen · 60 lines · 21 tokens per session scan A 0997c393cc23
issue-track is a skill published in the GitHub repository alexmond/jhelm (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 344 once invoked, about $0.0001 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
kanban
Use when work has several deliverables, tickets, or delegates: board, WIP 1 writer + 2 review, pull rule, Definition of Done, findings fixed or filed.
java
Use when writing, reviewing or refactoring modern Java (21+, 25 LTS) — records and sealed interfaces as algebraic data types, exhaustive pattern-matching switch over instanceof ladders, virtual-thread concurrency, structured concurrency and ScopedValue replacing ThreadLocal, Stream and Optional pipelines…
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
zhihu-search
A search skill for finding content on Zhihu, a Chinese question-and-answer and article platform, through its search API.
spring-plugin-issue-delivery
Orchestrates explyt/spring-plugin GitHub issues end to end by routing work to Test, Code, Review and Ask agents and forks: one writer per checkout, parallel lanes in sibling git worktrees, stacked PRs for dependent work, briefs, verification of every returned result, PR split and merge order, refreshing open PRs after…