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 skills/batteryshark/rekit/js-covert-scannpx skills add batteryshark/rekit --skill js-covert-scangit 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/js-covert-scan)<a href="https://agentmods.dev/skills/batteryshark/rekit/js-covert-scan"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/js-covert-scan.svg" alt="Measured on agentmods" 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.00142 | $0.01030 |
| Opus 5 | $0.00071 | $0.00515 |
| Sonnet 5 | $0.00028 | $0.00206 |
| Haiku 4.5 | $0.00014 | $0.00103 |
Grade A, and why
js-covert-scan 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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JavaScript Covert-Tactics Scanner
Detect the tactics code uses to hide what it does in JavaScript/TypeScript, and emit atoms a caller can reason over. Static, read-only, pure-stdlib.
When to use
You suspect a file is doing something it doesn't advertise — behaving differently
for some users, smuggling signal through text, or hiding strings/logic from a casual
read or a strings dump. This scanner surfaces the tactics; it does not decide
intent. Run it on a file or a whole package.
What it detects — real parallax atoms, tagged method="covert-scan"
Every finding is emitted as a judgment-free parallax atom with method: "covert-scan"; the downstream lens makes the obfuscation/evasion judgment from that
provenance. The per-tactic note preserves exactly which hiding tactic was seen (so
XFRM.UNICODE findings still say "bidi control char" vs "confusable homoglyph", and
ENVI.ENVCHECK findings still say "timezone-conditional" vs "geolocation check").
XFRM.UNICODE — hidden in text you can't see or can't tell apart:
- zero-width / format / control characters (U+200B, U+FEFF, soft hyphen, word joiner, variation selectors, tag chars…).
- bidirectional control characters (the "Trojan Source" reordering attack: source that reads differently than it compiles).
- confusable characters standing in for ASCII: fancy apostrophes / quotes (e.g.
U+2019 ’,U+02BC ʼ,U+02B9 ʹ), non-breaking / ideographic spaces, look-alike dashes, and Cyrillic/Greek/fullwidth letters posing as Latin.
XFRM.BITWISE — XOR of character codes (a common way to keep strings out of a
plain strings dump).
XFRM.ENCODE — machine-hidden strings:
- strings assembled from
String.fromCharCode(…)number lists. - long
\xNN/\uNNNNescaped string blobs.
LOAD.EVAL — eval(…) / new Function(…) dynamic execution.
ENVI.ENVCHECK — environment-keyed conditional behavior (act differently for specific victims / dodge analysis):
- timezone checks:
Intl.DateTimeFormat().resolvedOptions().timeZone, timezone name literals. - locale checks:
navigator.language, resolved locale. - geolocation / IP-geo checks.
- proxy /
*_PROXYenv checks.
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.
- 6d ago First seen · 81 lines · 142 tokens per session scan A 4029ddeef47f
js-covert-scan is a skill published in the GitHub repository batteryshark/rekit (10 stars, last pushed 28d ago), licensed Apache-2.0. It adds 142 tokens to every session and 1,030 once invoked, about $0.0007 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…