Borrowing it
Nothing to install: this file belongs to ractive/hyalo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ractive/hyalo/main/.claude/skills/security-audit/SKILL.mdgit clone --depth 1 https://github.com/ractive/hyaloWrote 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/ractive/hyalo/security-audit)<a href="https://agentmods.dev/skills/ractive/hyalo/security-audit"><img src="https://agentmods.dev/badge/skills/ractive/hyalo/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/ractive/hyalo/security-audit"><img src="https://agentmods.dev/badge/skills/ractive/hyalo/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.00150 | $0.01720 |
| Opus 5.5 | $0.00060 | $0.00688 |
| Sonnet 5.5 | $0.00030 | $0.00344 |
| Haiku 4.5 | $0.00015 | $0.00172 |
Grade B, and why
security-audit scanned grade B with 1 finding 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 2mo 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Can download commands write to arbitrary paths? (overwriting ~/.ssh/authorized_keys, etc.) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
You are performing a security audit of a Rust codebase. Your goal is to find real, actionable security issues — not to generate a long list of theoretical concerns. Prioritize findings by actual risk: a leaked API key in a fixture is more urgent than a theoretical timing attack on a string comparison.
Audit Structure
Produce a report with these sections. For each section, only include findings — skip "PASS" items unless they are genuinely surprising or counterintuitive. A lean report focused on what needs fixing is more useful than one padded with confirmations of good practices. However, always check and report on dependencies (section 2) even if they look clean — dependency vulnerabilities are silent and a "no issues found" confirmation is valuable there.
1. Secrets & Sensitive Data Scan
This is often the highest-impact finding category because leaked secrets can be exploited immediately, unlike code vulnerabilities that require an attack vector. Scan systematically — open and read every non-binary file, don't just check whether directories are gitignored.
Where to look (read the actual files, don't just check if they exist):
- Test fixtures (JSON, YAML, TOML in
tests/orfixtures/dirs) — open each one and check for real-looking values - Documentation and knowledgebase files — read every
.mdfile in anydocs/,knowledgebase/, or similar directory. Look for infrastructure details, account references, "production" mentions, internal project names, and internal URLs. These files are easily overlooked but often contain the most revealing information about the real infrastructure behind the project - Agent memory and config (
.claude/directory tree) — check committed agent definitions, skill files, and memory indexes for private paths or personal details - Config files (
.env,.env.example,settings.json,settings.local.json) - OpenAPI specs or API reference files — these often contain example data copied from real responses
- Cargo.toml metadata (author emails, repository URLs)
- CI/CD configs
What ships with it
1 file 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.
- 2mo ago First seen · 137 lines · 150 tokens per session scan B 8fe49cf18d8b
security-audit is a skill published in the GitHub repository ractive/hyalo (27 stars, last pushed 5d ago), licensed MIT. It adds 150 tokens to every session and 1,720 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
digest
Write one page about an article, blog post, news item, release note, or talk (slides) from its URL into this Scraps wiki, without dialogue - a short summary of what the source says, linked to the pages the wiki already has. Use this when the user hands over the URL of something they read or want to keep up with and…
learn
Learn a source together with the user and record only what they understood as a new page in this Scraps wiki. Explains the source with a diagram anchored on the pages the wiki already has, checks comprehension with questions, then writes one page from the points that passed; when understanding is not reached, nothing…
ingest
Create a new scrap from a source (prompt, URL, or arbitrary markdown), update cross-links in related scraps, and run a sanity check. Use this when the user wants to add a scrap, summarize an article, save synthesized content to the wiki, or file back a Q&A result.
query
Answer questions about the wiki by searching, reading, and synthesizing relevant scraps with [[Title]] citations. Use this when the user wants to query the wiki, ask what they have written about a topic, compare scraps, find related notes, or pull a synthesized overview from existing scraps.
planning-with-scratchpad
Use when user explicitly requests planning with a scratchpad, or asks for persistent tracking of a complex task that the human can browse visually. Backs planning files with the scratch CLI so a pad's files are registered and viewable.