claudesec / rules
Cursor rule16 starsChanged 6 months agoMITView on GitHub
ClaudeSec project overview, layout, and core conventions
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,157 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- scanner/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/claude-agents-and-practices.mdcCursor rule
- .cursor/rules/markdown-quality.mdcCursor rule
- .cursor/rules/no-sensitive-paths.mdcCursor rule
- .cursor/rules/security-citations.mdcCursor rule
- ci-config-guard-claudesecSkill
- kcov-debugSkill
- lychee-redirect-triageSkill
- omc-referenceSkill
The file
We split this claudesec-project.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 30
New content: Place files in the appropriate directory above.
≈ “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
--- description: ClaudeSec project overview, layout, and core conventions alwaysApply: true --- # ClaudeSec Project ClaudeSec is a **DevSecOps toolkit** for AI-assisted secure development. Documentation is Markdown-only; no build system. ## Directory Layout - `docs/devsecops/` — DevSecOps pipeline and practices - `docs/github/` — GitHub security features - `docs/ai/` — AI and LLM security - `docs/guides/` — Step-by-step tutorials - `docs/compliance/` — NIST, ISO, ISMS-P compliance guides - `docs/architecture/` — Draw.io architecture/flow/security-domains diagrams (generated from scan data) - `docs/reports/` — Session reports, retrospectives, and generated scan/seminar collateral - `docs/plans/` — Strategy and planning documents - `assets/` — Logo and branding assets - `templates/` — Reusable config templates - `scanner/` — Security scanner CLI - `scripts/` — Automation scripts - `hooks/` — Claude Code security hooks - `examples/` — Example projects and configs ## Conventions - **File names**: kebab-case (e.g. `github-actions-security.md`). - **New content**: Place files in the appropriate directory above; do not add ad-hoc top-level folders.
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.