appsec
Skill0 starsChanged 6 months agoMITView on GitHub
Performs senior-grade application security code review: three-pass methodology, OWASP/CWE-oriented vulnerability analysis, language-specific dangerous patterns, cryptography checks, structured findings, and concrete remediations. Use when analyzing source code for security vulnerabilities, reviewing changes for AppSec issues, or when the user asks for a security review, threat modeling of implementation, or secure coding feedback.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- defi0x1/app-security-skillstheir own version, first seen Oct 20, 2026
- TelosTechnology/skillstheir own version, first seen Jul 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- TelosTechnology/skills★ 1same name
- defi0x1/app-security-skills★ 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 repository3 other files it gives its agents.
- benchmarkSkill
- learnSkill
- scoreboardSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 16
When this skill is active, you conduct secure code review with the rigor of a senior application security engineer.
- Distinctive: line 26
Read these modules in order (paths are relative to this skill folder).
≈ “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.
Files
AppSec Skill
When this skill is active, you conduct secure code review with the rigor of a senior application security engineer. Analyze source code for security vulnerabilities accordingly.
When to use
- Security review of files, directories, or pull requests
- Any request to find vulnerabilities, unsafe patterns, or crypto misuse
- Structured reporting that matches this repository’s finding schema
Before touching application code
Read these modules in order (paths are relative to this skill folder). They define mindset, methodology, coverage, and output rules.
- references/00-identity.md — mindset, expertise scope, hard rules
- references/01-methodology.md — three-pass code review
- references/02-vulnerability-classes.md — vulnerability catalog and detection
- references/03-language-specific.md — per-language dangerous patterns
- references/04-cryptography.md — cryptography checks
- references/05-output-format.md — structured findings
- references/06-remediation.md — code-level remediations
Invocation examples
Single file: load this skill, then analyze <path/to/file> for security vulnerabilities.
Directory: load this skill, then analyze all source files under <path/to/dir/> for security vulnerabilities.
Editors that support the Agent Skills layout discover this folder as a skill; load SKILL.md first, then the references/ chain it lists.
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.