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 skills add batteryshark/rekit --skill protection-surveygit clone --depth 1 https://github.com/batteryshark/rekitWrote 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/batteryshark/rekit/protection-survey)<a href="https://agentmods.dev/skills/batteryshark/rekit/protection-survey"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/protection-survey/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/batteryshark/rekit/protection-survey"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/protection-survey.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.00107 | $0.00471 |
| Opus 5 | $0.00053 | $0.00235 |
| Sonnet 5 | $0.00021 | $0.00094 |
| Haiku 4.5 | $0.00011 | $0.00047 |
Grade A, and why
protection-survey 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 9d 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
Source Protection Survey
Run a fast, read-only first pass over source code before deeper manual review. The
scanner reports protection mechanisms, not intent: each finding is a location,
matched indicator, confidence, and judgment-free PROT.* atom.
Usage
rekit run protection-survey ./source --format json
rekit run protection-survey ./main.rs --format text
rekit run protection-survey ./source --max-files 20000 --max-file-bytes 4194304
Workflow
- Scan the project root or a single source/build file.
- Rank categories by count and confidence.
- Review the reported lines in context; do not infer maliciousness from one API.
- Correlate multiple families—for example anti-debug checks plus executable-memory transitions plus runtime resolution—before drawing conclusions.
The scanner understands common source extensions for C-family languages, assembly,
Rust, Go, Python, JS/TS, JVM languages, C#, and Swift. It also examines build files
such as Cargo.toml, build.rs, Makefile, and CMakeLists.txt. Generated/vendor
trees are skipped by default.
Output and limits
JSON includes {ok, root, filesScanned, skipped, findingCount, categoryCounts, families, assessment, findings}. Each finding contains atom, confidence, file,
line, col, indicator, snippet, and method: "protection-survey".
Regex and co-occurrence heuristics are intentionally explainable. They can miss macro-generated or semantically disguised protections and can flag legitimate systems code. Treat the output as a review queue, not a verdict.
What ships with it
1 file 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.
- 9d ago First seen · 42 lines · 107 tokens per session scan A 5f1dde625c41
protection-survey is a skill published in the GitHub repository batteryshark/rekit (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 107 tokens to every session and 471 once invoked, about $0.0005 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…