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.
git clone --depth 1 https://github.com/isaacsight/kernelWrote 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/commands/isaacsight/kernel/security-audit)<a href="https://agentmods.dev/commands/isaacsight/kernel/security-audit"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/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/commands/isaacsight/kernel/security-audit"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/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.00000 | $0.00482 |
| Opus 5.5 | $0.00000 | $0.00193 |
| Sonnet 5.5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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 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.
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
Run a full security audit on the Kernel platform.
You are the Security Agent. Read .claude/agents/security.md for your full protocol and known exceptions.
Steps:
- Load memory — Call
agent_memory_readforsecurityagent - npm audit — Run
kernel_auditfor vulnerability scan and secrets detection - Secrets scan — Grep source code for hardcoded keys:
- Search
src/andtools/for:sk_live_,sk_test_,AKIA,ghp_,xox[bsa]-,-----BEGIN,SUPABASE_SERVICE_KEY - Check that
.envis in.gitignore
- Search
- Edge function auth — For each edge function in
supabase/functions/, verify JWT checking:- claude-proxy: MUST have JWT
- web-search: MUST have JWT
- create-checkout: MUST have JWT
- stripe-webhook: Uses Stripe signature (OK)
- shared-conversation: verify_jwt=false (KNOWN EXCEPTION)
- task-scheduler: verify_jwt=false (KNOWN EXCEPTION)
- send-notification: verify_jwt=false (KNOWN EXCEPTION)
- Client-side safety — Scan
src/for:eval(ornew Function(dangerouslySetInnerHTMLwithout sanitization- Hardcoded
localhostor127.0.0.1URLs
- RLS check — Run
kernel_db_schemaand verify tables have appropriate RLS policies - CORS check — Verify all edge functions include proper CORS headers
- Save findings — Call
agent_memory_writeforsecuritywith findings - Handoff — If issues affect deployment, call
team_handofftodevops
Report format:
# Security Audit — [date]
## Vulnerabilities (npm)
[critical/high/moderate/low counts]
## Secrets Scan
[PASS or findings]
## Edge Function Auth
[table of functions and their auth status]
## Client-Side Safety
[PASS or findings]
## Verdict: PASS / FAIL (any P0 = FAIL)
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 · 47 lines · 0 tokens per session scan A f4dd72b93e54
security-audit is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 tokens. 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-09-03.
security-audit compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| security-auditisaacsight/kernel | Command | 16 | 1mo ago | MIT | A | 0 | Claude Code |
| buildAzure/ai-gateway | Command | 5 | 10d ago | MIT | A | 0 | Claude Code |
| api-contract-reviewMozurok/fhorja.dev | Command | 10 | 28d ago | MIT | A | 64 | Claude Code |
| symfony-api-mcpgerard-labs/superpowers-api-platform | Command | 2 | 5mo ago | MIT | A | 17 | Claude Code |
| add-api-railwayAshikparvez89/larouex-fullstack-plugin | Command | 3 | 24d ago | MIT | A | 0 | Claude Code |
| multi-backendRohitBind123/claude-setup | Command | 2 | 6mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |