Borrowing it
Nothing to install: this file belongs to seed-hypermedia/seed. 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/seed-hypermedia/seed/main/.agents/skills/security-audit/SKILL.mdgit clone --depth 1 https://github.com/seed-hypermedia/seedWrote 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/seed-hypermedia/seed/security-audit)<a href="https://agentmods.dev/skills/seed-hypermedia/seed/security-audit"><img src="https://agentmods.dev/badge/skills/seed-hypermedia/seed/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/seed-hypermedia/seed/security-audit"><img src="https://agentmods.dev/badge/skills/seed-hypermedia/seed/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.00051 | $0.00659 |
| Opus 5.5 | $0.00020 | $0.00264 |
| Sonnet 5.5 | $0.00010 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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 7d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Audit the requested Seed surface, reproduce findings, and preserve evidence for later audit sessions.
Scope and resources
This workflow is opt-in. A security-related bug, test, or code comment does not activate it. Follow the user's requested audit scope; do not expand a routine fix into an audit.
Before auditing, read:
- Audit log: prior coverage, ruled-out hypotheses, and historical findings.
- Audit protocol: safety rules, review passes, reproduction requirements, severity rubric, and reporting format. Read the relevant phase before carrying it out.
- Electron checklist: the desktop app against Electron's security checklist, for audits that touch the desktop.
- Applicable repository guidance, including
AGENTS.local.mdwhen present.
Paths in protocol commands are relative to the repository root. The log contains historical observations, not proof of current behavior; verify relevant claims against the current checkout.
Workflow
- State the audit scope and planned passes. Read prior records before investigating candidates.
- Trace reachable entry points, guards, and attacker-satisfiable preconditions. Separate static hypotheses from reproduced findings.
- Reproduce each candidate with an asserting regression test or the protocol's controlled live-probe procedure. Record both failing-before and passing-after results; inability to run a check is a limitation, not a pass.
- Obtain approval for the fix plan before changing product code unless the requested scope and fix are already explicitly authorized. Keep tests and changes within that scope.
- Update the audit log with public-safe coverage and ruled-out results. Keep unfixed exploit details and probe output
in the gitignored
.ai/security/records described in the protocol. - Report results, limitations, and the actual delivery state. Commit, push, disclosure, and external workflow actions each require the applicable authorization; loading this skill grants none of those permissions.
What ships with it
4 files 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.
- 7d ago Changed · +2 lines 3e494da6f104
- 9d ago First seen · 54 lines · 51 tokens per session scan A 2f5be1192be5
security-audit is a skill published in the GitHub repository seed-hypermedia/seed (59 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 659 once invoked, about $0.0002 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.