full-audit
Skill0 starsChanged 13 days agoMITView on GitHub
Run a full authorized audit combining security and functional/visual testing, correlate findings across code, APIs, database and UI, and compute a coverage-qualified internal 1-5 star rating. Use when the user invokes full-audit or asks for a complete audit of their own authorized project.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- undark-ai/Meta-Ads-OStheir own version, first seen Nov 15, 2026
- AlexZio00/sovereign-skillstheir own version, first seen Nov 14, 2026
- Marco-Satis/claude-setuptheir own version, first seen Oct 20, 2026
- SpinaBuilds/full-audit-skilltheir own version, first seen Oct 13, 2026
- ArhamBafna/agent-skillstheir own version, first seen Oct 3, 2026
- Recusive/Skillstheir own version, first seen Mar 19, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- AlexZio00/sovereign-skills★ 158same name
- Recusive/Skills★ 2same name
- SpinaBuilds/full-audit-skill★ 1same name
- ArhamBafna/agent-skills★ 0same name
- Marco-Satis/claude-setup★ 0same name
- undark-ai/Meta-Ads-OS★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- functional-auditSkill
- security-auditor-proSkill
- security-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Run SECURITY and FUNCTIONAL in the same audit, then correlate: e.g.
- Distinctive: line 15
Start with step 1 (authorization and scope).
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
full-audit
Mode: FULL.
Load and follow the core procedure in ../security-auditor-pro/SKILL.md (relative to this skill's directory),
including its policy (../security-auditor-pro/references/POLICY.md), steps and hard rules.
Run SECURITY and FUNCTIONAL in the same audit, then correlate: e.g. a UI flow that exposes an API weakness, or a code finding confirmed visually. Finish with the rating (step 9) and the Markdown report.
Start with step 1 (authorization and scope). If scope is unknown, ask for it before doing anything else.
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.

