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 plan-issuegit 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/plan-issue)<a href="https://agentmods.dev/skills/alexmond/jhelm/plan-issue"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/plan-issue/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/plan-issue"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/plan-issue.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.00018 | $0.00688 |
| Opus 5.5 | $0.00007 | $0.00275 |
| Sonnet 5.5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
plan-issue 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Implementation for GitHub Issue #$ARGUMENTS
Produce a detailed, approvable implementation plan before writing any code.
Step 1: Read the issue and announce work started
gh issue view $ARGUMENTS
Extract:
- Goal / user-facing behaviour
- Explicit requirements and acceptance criteria
- Any referenced files, classes, or issues
Then post a comment to announce work has started:
gh issue comment $ARGUMENTS --body "🔧 **Work started** — exploring the codebase and drafting an implementation plan."
Step 2: Explore the codebase
Use Glob and Grep (or the Explore agent for broad searches) to locate:
- Files to create — identify the right package and naming convention by finding similar classes
- Files to modify — find every call site or injection point that needs updating
- Tests to create/update — find the existing test class for each file being modified
- Relevant patterns — read 1–2 existing similar classes to match structure (imports, annotations, error handling)
Key places to always check:
jhelm-core/src/main/java/org/alexmond/jhelm/core/— action classes, models, interfacesjhelm-kube/src/main/java/— Kubernetes client implementationjhelm-cli/src/main/java/— CLI commands (Picocli)- Matching test directories for each module
Step 3: Write the plan
Write the plan to /tmp/plan-$ARGUMENTS.md using this structure:
# Plan: <Issue Title> (Issue #$ARGUMENTS)
## Context
<2–3 sentences on what currently exists and what is missing>
## Files to Create
### 1. `path/to/NewClass.java`
- Purpose and key methods
- Important implementation notes
## Files to Modify
### N. `path/to/ExistingClass.java`
- What changes and why
- Code sketch if helpful
## Test Files to Create/Update
### N+1. `path/to/NewClassTest.java`
- Test cases to cover (success, error, edge cases)
## Verification
```bash
./mvnw test -pl <module>
./mvnw install
./mvnw spring-javaformat:apply && ./mvnw validate
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 · 103 lines · 18 tokens per session scan A 6db9a4717e9c
plan-issue is a skill published in the GitHub repository alexmond/jhelm (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 18 tokens to every session and 688 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
release-notes
Update CHANGELOG.md and README.md for an Azure SDK for Java package based on a GitHub PR. Use when the user wants to write or update release notes, changelogs, or readme docs from a PR reference.
codegen
Generate code from TypeSpec via tsp-client (update, sync, generate). Requires a tsp-location.yaml in the current working directory. Supports updating the commit hash before running.
feature-workflow
Taking a multi-PR feature from "shape unknown" to merged without five review rounds per PR: spike until interfaces stop moving, write the contract, cut PRs along contract seams, one review per PR. Use when starting a feature that touches more than one lifecycle object or public interface, when a PR review keeps…
release-plugin
Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.
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…
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.