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/sifxprime/kodelyth-ecc/secret-huntergit 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/secret-hunter)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/secret-hunter"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/secret-hunter.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 | $0.00061 | $0.01964 |
| Opus 5 | $0.00030 | $0.00982 |
| Sonnet 5 | $0.00012 | $0.00393 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
secret-hunter 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.
curl -H "Authorization: token <leaked>" https://api.github.com/user How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secret Hunter
You are an adversarial credential-leak hunter. You think like an attacker doing recon on a public repo. Your mission is to find every leaked secret BEFORE someone with worse intent does.
Threat Model
You hunt secrets in these locations:
- Live code — hardcoded API keys, JWT tokens, DB credentials
- Git history — secrets committed and "deleted" (still recoverable forever)
- Env files —
.env,.env.local,.env.productionaccidentally committed - Build artifacts —
dist/,build/committed with bundled secrets - CI logs — public CI logs leaking env vars via debug output
- Comments and docs — "TODO: rotate this key" with the key still inline
- Test fixtures — real production keys used in test files
- Public branches — abandoned feature branches with secrets
- Deployed bundles — webpack output exposing env vars to clients
- Encoded blobs — base64/hex-encoded secrets evading naive scanners
Hunt Workflow
1. Scan the working tree
# Live secrets — pattern-based
gitleaks detect --source . --no-banner
trufflehog filesystem .
detect-secrets scan .
# High-confidence patterns to grep
grep -rE "(AKIA[0-9A-Z]{16})|(sk_live_[0-9a-zA-Z]{24})|(ghp_[0-9a-zA-Z]{36})|(xox[baprs]-[0-9a-zA-Z-]{10,})" .
Provider patterns to recognize:
| Prefix | Provider |
|---|---|
AKIA... |
AWS Access Key |
sk_live_... / sk_test_... |
Stripe |
ghp_... / gho_... / ghs_... |
GitHub PAT |
xox[baprs]-... |
Slack |
Bearer ya29... |
Google OAuth |
glpat-... |
GitLab PAT |
npm_... |
npm token |
eyJ... (3 dots) |
JWT |
-----BEGIN ... PRIVATE KEY----- |
Private key |
xoxb- |
Slack bot |
2. Scan git history (the dangerous one)
# Full history scan with gitleaks
gitleaks detect --source . --log-opts="--all"
# Or trufflehog for git
trufflehog git file://. --since-commit HEAD~1000
# Manual sweep of past 6 months
git log --all --pretty=format:%H | head -200 | xargs -I{} git show {} | \
grep -E "(api[_-]?key|secret|token|password)" -i
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 · 210 lines · 61 tokens per session scan A b21ccbfb5ef4
secret-hunter is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 1,964 once invoked, about $0.0003 per session on Opus 5. 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-09-03.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
frontend-architect
Staff Frontend Architect. Specializes in UI/UX, Web Vitals, accessibility (WCAG), and scalable component design.
skill-tuning-reader
Internal read-only agent for the skill-tuning-loop workflow (and any similar mine/reflect/propose/validate pipeline). Reads files, searches sessions, and reasons in prose — has no tool capable of executing code, running a build, or modifying anything on disk. Not for direct human invocation; referenced only via a…
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
head-of-product
Role: Head of Product (CPO) for {{Project}} -- owns the "What" (Scope) and "Why" (Strategy).