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/.codex/skills/keyleak-audit/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-audit)<a href="https://agentmods.dev/skills/amal-david/keyleak-detector/keyleak-audit"><img src="https://agentmods.dev/badge/skills/amal-david/keyleak-detector/keyleak-audit/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-audit"><img src="https://agentmods.dev/badge/skills/amal-david/keyleak-detector/keyleak-audit.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.00290 |
| Opus 5.5 | $0.00000 | $0.00116 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
keyleak-audit 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.
What it actually says
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.
Prefer keyleak audit <target> as the single front door. A domain target is exact
host by default; require explicit --include-subdomains only for authorized
registrable-domain discovery and crawling. Require
both --authorized-scope and --attest-network-scope before active network
scans, exploit-validation, BaaS validation, or two-user access-control checks.
Treat the scope as an operator attestation, not technical proof of authorization.
Use --plan for a non-executing, redacted plan.
Under --offline, do not run a URL or domain audit; use a plan, local path, or
archive because Chromium is outside Python's socket-level offline guard.
Use --assessment-mode blue-team, red-team, or balanced to change only the
evidence framing; it never expands tool or network permissions.
Return BLOCK SHIP, REVIEW, or SAFE TO SHIP first, then artifact directory,
severity counts, validated or confirmed evidence, skipped phases, retest command,
and next probes. Do not report AI-inferred exploitability without deterministic
KeyLeak evidence.
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 · 23 lines · 0 tokens per session scan A 13141fa3b42e
keyleak-audit 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 290 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.