Borrowing it
Nothing to install: this file belongs to katopz/katgpt-rs. 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/katopz/katgpt-rs/develop/.agents/skills/security-audit/SKILL.mdgit clone --depth 1 https://github.com/katopz/katgpt-rsWrote 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/katopz/katgpt-rs/security-audit)<a href="https://agentmods.dev/skills/katopz/katgpt-rs/security-audit"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/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/katopz/katgpt-rs/security-audit"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/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.00070 | $0.03222 |
| Opus 5.5 | $0.00028 | $0.01289 |
| Sonnet 5.5 | $0.00014 | $0.00644 |
| Haiku 4.5 | $0.00007 | $0.00322 |
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 2d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Find vulnerabilities that violate a real trust boundary, then hand the owner the source
evidence, a safe reproduction, a priority, and the smallest effective fix. Adapted for
this Rust workspace from Cloudflare's security-audit-skill (MIT — provenance at the
bottom). A candidate without a concrete affected principal, resource, or security
outcome is not a finding — it is a hardening note.
Three modes
- Guidance mode (default): the user asks a security question or wants a focused review of one surface. Use only the relevant sections below. Do not create output directories, do not write report artifacts, do not launch the full workflow.
- Full audit mode: the user explicitly asks to audit or pen-test a codebase, or wants a full / comprehensive / end-to-end review, or asks for report artifacts. Run all six phases and write the artifact set.
- Post-flow pass: the user asks to security-review a landed diff, branch, or PR before merge ("review this diff", "security-check these changes", a pre-merge gate). Diff-scoped — see the dedicated section below. Never a whole-repo claim.
If the request could mean either, ask one focused question before writing any file.
Execution safety — always, both modes
- Source inspection is read-only. Never edit, format, or "fix" the target while auditing it.
- Run target-controlled code (builds, tests, fuzzers, fixture processors) only inside a
sandbox: no external network, an explicit allowlisted environment, read-only target,
bounded CPU / memory / wall-clock. If the sandbox cannot be enforced, do not execute
target code — record a
needs_validationfinding naming the missing control and the safe validation plan. - Never probe deployed endpoints, live chain RPC, shared services, production keys, or another user's data. Dummy principals and fixtures only. Never send real spend, never stress-test availability against a live process.
- Never print, copy, or commit secret values found during the audit (env files, keys, tokens). Report the path and shape, redact the value. This overrides any "include evidence" instruction.
- Pin the target before verdict work — record repo + commit sha (and dirty state) in the run metadata. Quotes against an unpinned tree are worthless; a dirty worktree can make an uncommitted edit look like a finding.
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.
- 2d ago Changed · +47 lines d80dcd068964
- 10d ago First seen · 173 lines · 70 tokens per session scan A a75b75576ceb
security-audit is a skill published in the GitHub repository katopz/katgpt-rs (140 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 3,222 once invoked, about $0.0003 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-10-20.
Other skills, from other repositories
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
azure-keyvault-secrets-rust
Client library for Azure Key Vault Secrets — secure storage for passwords, API keys, and other secrets.
rust-error
Define, wrap, convert, classify, report or test Rust error types in litellm-rust with thiserror. Use when adding an error type or variant, mapping one crate's error into another, turning an error into a gateway response or Python exception, deciding retry or fault from an error, or replacing call sites that build…