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/alexmond/jhelm/security-auditnpx 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.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00515 |
| Opus 5 | $0.00011 | $0.00258 |
| Sonnet 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 4d 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.
- 4d ago First seen · 68 lines · 22 tokens per session scan A 22102095e5fd
security-audit is a skill published in the GitHub repository alexmond/jhelm (4 stars, last pushed 10d ago), licensed Apache-2.0. It adds 22 tokens to every session and 515 once invoked, about $0.0001 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
evergreen
Evergreen CI infrastructure, configuration validation. Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix.
sync-agents-docs
Sync AGENTS.md files, skills, and references after buildSrc or convention changes. Use after modifying build plugins, formatting rules, testing conventions, or task names to keep documentation consistent.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.