Borrowing it
Nothing to install: this file belongs to Amal-David/keyleak-detector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Amal-David/keyleak-detector/main/.claude/skills/keyleak-verify/SKILL.mdgit clone --depth 1 https://github.com/Amal-David/keyleak-detectorWrote 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/amal-david/keyleak-detector/keyleak-verify)<a href="https://agentmods.dev/skills/amal-david/keyleak-detector/keyleak-verify"><img src="https://agentmods.dev/badge/skills/amal-david/keyleak-detector/keyleak-verify/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/amal-david/keyleak-detector/keyleak-verify"><img src="https://agentmods.dev/badge/skills/amal-david/keyleak-detector/keyleak-verify.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.00000 | $0.00806 |
| Opus 5.5 | $0.00000 | $0.00322 |
| Sonnet 5.5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
keyleak-verify 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 15d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KeyLeak Audit Router
Use this skill when a prompt asks for a security audit, vulnerability detection, pentest, bug bounty scan, checking an app/repo for security issues, deployment ship readiness, or whether a finding is exploitable.
Route
Prefer the single front door:
keyleak audit <target> --intent security-audit
Choose intent from the user wording:
ship: release, deploy, launch gate, preview readiness.security-audit: security audit, vulnerability detection, check this repo/app.bug-bounty: bug bounty, pentest, is this exploitable, authorized target testing.
Choose --assessment-mode blue-team for defensive remediation, red-team for
bounded attacker-perspective questions, or leave the default balanced. The mode
changes reporting focus only; it never expands tool or network permissions.
Choose target from the prompt:
- local path or repo: pass the path directly.
- archive: pass the zip/tar path directly.
- one preview/live URL: pass the full URL.
- whole site/domain: pass the domain.
Authorization Gate
Never run active network scans, exploit-validation, BaaS probes, or two-user
access-control checks without both an explicit --authorized-scope and
--attest-network-scope. If either is absent, request only the missing input or
inputs and stop; do not retry the active phase until both are present.
If the operator requested --offline, do not run URL or domain audits: use
--plan, a local path, or an archive instead because Chromium is a separate
process outside Python's socket-level offline guard.
Good scope examples:
owned repoowned preview deploymentowned domain + staging accountsauthorized bug bounty scope: app.example.com
For an authenticated single-user browser scan, accept only a short-lived, operator-managed Playwright storage-state file with restrictive permissions. The audit command intentionally does not accept bearer tokens or cookies on the command line, and its two-user comparison remains unavailable until a non-argv credential handoff is implemented. Do not request admin credentials.
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.
- 15d ago First seen · 110 lines · 0 tokens per session scan A 163fdcfbeb4a
keyleak-verify is a skill published in the GitHub repository Amal-David/keyleak-detector (275 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 806 tokens. 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-10-12.
Other skills, from other repositories
prowler-compliance
Creates, syncs, audits and manages Prowler compliance frameworks end-to-end. Covers the two supported JSON schemas (universal multi-provider and legacy per-provider), the SDK model tree (legacy attribute classes, universal ComplianceFramework, ConfigRequirements guardrails), output formatters (legacy per-framework +…
prowler-attack-paths-query
Creates Prowler Attack Paths openCypher queries using the Cartography schema as the source of truth for node labels, properties, and relationships. Covers Prowler-specific additions (Internet node, ProwlerFinding, internal isolation labels), $provideruid scoping, and list-property item nodes with typed HAS edges that…
django-drf
Django REST Framework patterns. Trigger: When implementing generic DRF APIs (ViewSets, serializers, routers, permissions, filtersets). For Prowler API specifics (RLS/RBAC/Providers), also use prowler-api.
django-migration-psql
Reviews Django migration files for PostgreSQL best practices specific to Prowler. Trigger: When creating migrations, running makemigrations/pgmakemigrations, reviewing migration PRs, adding indexes or constraints to database tables, modifying existing migration files, or writing data backfill migrations. Always use…
prowler-api
Prowler API patterns: RLS, RBAC, providers, Celery tasks. Trigger: When working in api/ on models/serializers/viewsets/filters/tasks involving tenant isolation (RLS), RBAC, or provider lifecycle.
framework-compliance-triage
Make a cloud account compliant with a security or industry framework using Prowler Cloud.