llm-app-review
Skill1 starsChanged 2 days agoLicence not identifiedView on GitHub
Read-only, line-by-line review of the code of an app that uses an LLM, treating the model as untrusted, expensive and non-deterministic. Looks for outside text reaching the prompt (direct and indirect prompt injection) and what the model does next, tools with excess permissions, model output used unvalidated, uncapped cost (unlogged retries, timeouts that do not cancel, unbounded loops), prompts asking for what the code does not do, model evaluations that are not comparable, secrets or PII sent to the provider or logs, goals met to the letter but not in intent, and provider outages passed off as valid responses. Each finding brings path:line, sequence and a concrete input. Reports and stops. Use it for "review my LLM app", "prompt injection audit", "is my agent safe with tools". Not for RAG design or model choice (architecture-review). Also triggers on Spanish requests such as "revisa el uso del LLM", "¿mi agente es vulnerable a prompt injection?" or "¿cuánto gasta mi app en el modelo?".
- Reads credentials
In this repository10 other files it gives its agents.
- api-security-reviewSkill
- apply-remediationSkill
- architecture-reviewSkill
- code-structureSkill
- correctness-reviewSkill
- data-consistencySkill
- implicit-state-machinesSkill
- infra-reviewSkill
- perf-diagnosisSkill
- repo-audit-swarmSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
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
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.

