agentleFS
Amal-DavidAmal-David/keyleak-detector/llms.txt

keyleak-detector

llms.txt277 starsChanged 2 months agoMITView on GitHub

Local evidence collection and remediation verification for security agents. Start with keyleak capabilities --json for the installed version's supported checks, skill routes, network requirements, registered patterns and coverage limitations. Pattern matches and correlations are not proof of exploitation. Inspect validation status and incomplete coverage before making a release decision. Skills are distributed in the repository and require an approved CLI installation. This index is not proof of installation, marketplace listing, or search indexing.

  • In this repositoryOne other file it gives its agents.

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with keyleak capabilities --json for the installed version's supported checks, skill routes, network requirements, registered …

    line 5

≈ “Common” is an estimate: at least 1 in 5 of the 3,727 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# KeyLeak

> Local evidence collection and remediation verification for security agents.

Start with `keyleak capabilities --json` for the installed version's supported checks,
skill routes, network requirements, registered patterns and coverage limitations.
Pattern matches and correlations are not proof of exploitation. Inspect validation
status and incomplete coverage before making a release decision.

## Skills
- [Audit planning](.codex/skills/keyleak-audit/SKILL.md): Discover checks and preview a defensive audit.
- [Local review](.codex/skills/keyleak-local-review/SKILL.md): Secrets, Python serialization, archive evidence and repository hygiene.
- [Agent assets](.codex/skills/keyleak-agent-assets/SKILL.md): Credential checks for skills, agent rules and MCP settings.
- [Report triage](.codex/skills/keyleak-report-triage/SKILL.md): Review redacted evidence, suppressions, coverage and remediation.

## Documentation
- [Setup and usage](README.md)
- [Flow audit and ecosystem survey](docs/AGENT_INTEGRATION_AUDIT.md)

Skills are distributed in the repository and require an approved CLI installation.
This index is not proof of installation, marketplace listing, or search indexing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.