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 security-auditgit 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/security-audit)<a href="https://agentmods.dev/skills/alexmond/jhelm/security-audit"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/security-audit/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/security-audit"><img src="https://agentmods.dev/badge/skills/alexmond/jhelm/security-audit.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.00022 | $0.00515 |
| Opus 5.5 | $0.00009 | $0.00206 |
| Sonnet 5.5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
security-audit 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
Security Audit for jhelm
Scan the codebase (or specific module/file) for common security vulnerabilities.
Scope
If $ARGUMENTS is provided, limit the scan to that module or path. Otherwise, scan all modules.
Checks to Perform
1. Path Traversal
Search for file path construction from untrusted input:
Grep for: new File(.*,.*getName|new File(.*,.*entry|Path.of(.*input|Paths.get(.*input
Verify each hit has canonical path validation or sanitization.
2. Command Injection
Search for Runtime.exec, ProcessBuilder with user input:
Grep for: Runtime.getRuntime|ProcessBuilder|\.exec\(
Verify arguments are not constructed from user input without sanitization.
3. YAML Deserialization
Search for unsafe YAML parsing:
Grep for: new Yaml\(\)|Yaml.load\(|ObjectMapper.*readValue.*untrusted
Verify SnakeYAML SafeConstructor is used, or Jackson is configured safely.
4. XML External Entity (XXE)
Search for XML parsing without disabling external entities:
Grep for: DocumentBuilder|SAXParser|XMLReader|TransformerFactory
5. Sensitive Data Exposure
Search for credentials, tokens, or keys in code:
Grep for: password|secret|token|apiKey|private.key (case-insensitive, exclude test files)
Verify no hardcoded credentials exist.
6. Input Validation at Boundaries
Check REST endpoints and CLI argument handlers validate input:
- Chart names, repository URLs, file paths from user
- OCI registry responses
- Helm chart metadata (Chart.yaml fields)
Report Format
| Severity | Location | Issue | Recommendation |
|---|---|---|---|
| CRITICAL | file:line | Description | Fix suggestion |
| HIGH | file:line | Description | Fix suggestion |
| MEDIUM | file:line | Description | Fix suggestion |
| LOW | file:line | Description | Fix suggestion |
Report only confirmed findings, not theoretical risks. If clean, say "No vulnerabilities found."
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 · 68 lines · 22 tokens per session scan A 22102095e5fd
security-audit is a skill published in the GitHub repository alexmond/jhelm (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 515 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
effective-java
Generate and review Java code using patterns and best practices from Joshua Bloch's "Effective Java" (3rd Edition). Use this skill whenever the user asks about Java best practices, API design, object creation patterns, generics, enums, lambdas, streams, concurrency, serialization, method design, exception handling, or…
pr-review
Review of a PR, branch, or your own uncommitted work across eight dimensions — security, correctness, test coverage, API/compatibility, usability, documentation, code quality, performance. Sizes the diff, reviews inline or fans out reviewers off a shared brief, verifies findings against code, reports a grouped list…
code-review
Perform a pedantic, multi-perspective code review on the current diff or git changes against the styleguide and software engineering best practices.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
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.