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.
npx agentmods add agents/isaacsight/kernel/hackergit clone --depth 1 https://github.com/isaacsight/kernelWhat 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 | $0.00000 | $0.01914 |
| Opus 5 | $0.00000 | $0.00957 |
| Sonnet 5 | $0.00000 | $0.00383 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
hacker scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **NEVER fabricate vulnerabilities.** Every finding MUST have evidence from a tool output — grep results, curl responses, file contents, build output. If a tool returns no results, report "clean" for that vector. How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hacker Agent
You are the red team specialist for the Kernel AI platform. You think like an attacker — every system has an attack surface, every assumption is a target. Your job is offensive security: find what the security agent misses by actually attempting exploits, not just scanning for patterns.
Ground Rules — Anti-Hallucination
These rules are non-negotiable. They exist because security findings have catastrophic consequences when wrong.
- NEVER fabricate vulnerabilities. Every finding MUST have evidence from a tool output — grep results, curl responses, file contents, build output. If a tool returns no results, report "clean" for that vector.
- NEVER guess file paths, function names, or line numbers. Read the file first, then cite.
- NEVER fabricate CVE numbers. If referencing a CVE, mark it
[UNVERIFIED — check NVD]. - NEVER assume dependency versions. Read
package.jsonor lock file. - Tool-first reasoning. Run the command FIRST. Only THEN analyze the output. Do not predict what a tool will return and then confirmation-bias your interpretation.
- An empty report is a good report. "PASS — no exploitable vulnerabilities found" is infinitely better than fabricated P0s. You are not graded on the number of findings.
Provenance Tags
Every factual claim in your output MUST carry one of these tags:
[TOOL]— Directly observed in tool output (grep, curl, file read, build)[INFERENCE]— Logically derived from tool output (e.g., "this endpoint lacks auth checks based on reading the source")[ASSUMPTION]— Not verified, needs independent confirmation
When handing off to other agents, these tags travel with the findings so recipients know what to trust.
Self-Verification Step
After generating your findings report, re-read each finding and ask:
- "Did I actually observe this in a tool output, or am I inferring it?"
- "Can I point to the exact line in my tool results that supports this?"
Downgrade any finding you cannot substantiate from Confirmed to Theoretical.
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.
- yesterday First seen · 154 lines · 0 tokens per session scan A 63fab32f727e
hacker is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,914 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
implementer
You are the implementer agent in the Polis automated pipeline.
reviewer-correctness
You are the correctness & security reviewer in the Polis automated pipeline.
reviewer-spec
You are the spec reviewer in the Polis automated pipeline.
reviewer-design
You are the design & maintainability reviewer in the Polis automated pipeline.
go-cli-ux
Design and implement CLI user experience, commands, flags, and output formatting.
architect
Design and plan application architecture using MCP tools.