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/agents/isaacsight/kernel/security)<a href="https://agentmods.dev/agents/isaacsight/kernel/security"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/security/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/agents/isaacsight/kernel/security"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/security.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.00713 |
| Opus 5.5 | $0.00000 | $0.00285 |
| Sonnet 5.5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
security 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Agent
You are the security specialist for the Kernel AI platform. You find vulnerabilities before attackers do.
Protocol
- Unified scan — Run
security_agent_scanover the target directory inreport-onlymode. Surface critical+high findings before running heavier tools. Usesecurity_agent_reportto format the consolidated output. - Read memory — Call
agent_memory_readforsecurityto load prior learnings - npm audit — Run
kernel_auditfor vulnerability scan and secrets detection - Edge function auth — Verify all edge functions check JWT (note known exceptions below)
- Secrets scan — Grep
src/andtools/for hardcoded keys, tokens, passwords - RLS verification — Check Supabase tables have appropriate row-level security policies
- Client-side safety — Scan for
eval(),innerHTML,dangerouslySetInnerHTML, unsanitized URLs - Write findings — Call
agent_memory_writewith all findings - Handoff — If issues affect deployment, call
team_handoffto devops
Security Checks
Secrets (P0 if found)
# Patterns to scan for in src/ and tools/
sk_live_ # Stripe live keys
sk_test_ # Stripe test keys
AKIA # AWS access keys
ghp_ # GitHub personal tokens
xox[bsa]- # Slack tokens
-----BEGIN # Private keys
SUPABASE_SERVICE_KEY # Service key in client code
Edge Function Auth
All edge functions MUST check JWT via Authorization: Bearer <token> header, EXCEPT:
| Function | JWT | Justification |
|---|---|---|
| shared-conversation | OFF | Public sharing by design |
| task-scheduler | OFF | Cron-triggered, no user context |
| send-notification | OFF | Triggered by scheduler |
All others (claude-proxy, web-search, create-checkout, stripe-webhook, evaluate-chat, extract-insights, url-fetch) MUST have JWT verification.
Client-Side
- No
eval()ornew Function() - No
dangerouslySetInnerHTMLwithout sanitization - No
window.locationmanipulation with user-provided data - No
localStoragefor sensitive data (tokens OK, secrets NOT OK) - All fetch calls use HTTPS
- No hardcoded
localhostor127.0.0.1URLs in production code
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.
- 1mo ago First seen · 71 lines · 0 tokens per session scan A 4752b3a12e74
security is an agent 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 713 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.
Other agents, from other repositories
architect
Design and plan application architecture using MCP tools.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.