security-agent-skills / rules
Cursor rule4 starsChanged 3 months agoMITView on GitHub
This repository provides a curated library of security testing skills for AI agents. Skills are organized by domain under skills/. When a security-related task is detected, Cursor should: Run ./install.sh --agent cursor to install skills into .cursor/skills/. Use --copy for copy mode (default is symlink). See catalog.yaml for the machine-readable index of all skills, domains, and metadata.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-mcp-securitySkill
- modern-attack-surfacesSkill
- offensive-toolkitSkill
- security-and-hardeningSkill
- security-auditSkill
- security-code-reviewSkill
- ctf-jail-escapeSkill
- ctf-kernel-exploitationSkill
- ctf-misc-toolkitSkill
- ctf-orchestratorSkill
- ctf-playbookSkill
- ctf-technique-atlasSkill
- ctf-training-loopSkill
- ctf-web-exploitationSkill
- ctf-writeup-disciplineSkill
- ctf-writeup-screenshotsSkill
- binary-exploitationSkill
- crypto-attack-patternsSkill
- crypto-ctf-attacksSkill
- cryptography-fundamentalsSkill
- crypto-toolkitSkill
- encoding-realignmentSkill
- exploit-developmentSkill
- exploit-poc-builderSkill
- kernel-exploitationSkill
- zero-day-huntingSkill
- bluetooth-jammer-sweepSkill
- esp32-serial-diagSkill
- flipper-zero-backupSkill
- flipper-zero-firmwareSkill
- hardware-iot-hackingSkill
- nrf24-bitbang-spiSkill
- rf-jammer-firmware-portSkill
- rf-multi-protocol-jammerSkill
- smart-card-driver-debugSkill
- smart-card-usb-directSkill
- wifi-deauth-jammerSkill
- wifi-dualband-jammerSkill
- advanced-pentestSkill
- network-pentestSkill
- pentest-quick-checklistSkill
- pentest-tool-referenceSkill
- pentest-tool-setupSkill
- pentest-workflowSkill
- advanced-attack-chainsSkill
- autonomous-pentest-scannerSkill
- intranet-pentest-advancedSkill
- pentest-report-generatorSkill
- post-exploitation-opsSkill
- professional-pentest-guideSkill
- chatgpt-web-relaySkill
- darkweb-researchSkill
- email-osint-investigationSkill
- local-network-reconSkill
- network-device-reconSkill
- osint-frameworkSkill
- osint-recon-modelSkill
- parallel-intel-gatheringSkill
- reconnaissance-opsSkill
- The first 60 shown.
The file
We split this security-agent-skills.mdc into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
When a security-related task is detected, Cursor should:
- Very specific: line 12
Check skills/<domain>/<skill-name>/SKILL.md for relevant guidance.
- Distinctive: line 13
Follow any references, scripts, or validation steps linked from the skill.
- Distinctive: line 14
Prefer repo-local skill documentation over generic heuristics.
- Very specific: line 31
Run ./install.sh --agent cursor to install skills into .cursor/skills/.
- Very specific: line 32
Use --copy for copy mode (default is symlink).
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
# Cursor Project Rules — Security Agent Skills ## Overview This repository provides a curated library of security testing skills for AI agents. Skills are organized by domain under `skills/`. ## Skill Discovery When a security-related task is detected, Cursor should: 1. Check `skills/<domain>/<skill-name>/SKILL.md` for relevant guidance. 2. Follow any references, scripts, or validation steps linked from the skill. 3. Prefer repo-local skill documentation over generic heuristics. ## Domains - `skills/recon/` — OSINT, reconnaissance, subdomain discovery - `skills/web-pentest/` — web application penetration testing - `skills/network-pentest/` — network-level penetration testing - `skills/exploit-dev/` — exploit development and vulnerability research - `skills/reverse-engineering/` — binary analysis, decompilation, RE - `skills/ctf/` — capture-the-flag methodologies and toolkits - `skills/post-exploitation/` — post-exploitation operations - `skills/cloud-security/` — cloud security assessment - `skills/hardware-iot/` — hardware hacking and IoT security - `skills/security-orchestrator/` — cross-domain attack chain coordination ## Installation Run `./install.sh --agent cursor` to install skills into `.cursor/skills/`. Use `--copy` for copy mode (default is symlink). ## Catalog See `catalog.yaml` for the machine-readable index of all skills, domains, and metadata.
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.

