apex-agents / rules
Cursor rule1 starsChanged todayMITView on GitHub
Agent: Dependency Vulnerability Scanner - security specialist from Apex Agents
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,144 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 repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/apex-api-microservices-lead.mdcCursor rule
- .cursor/rules/apex-appsec-auditor.mdcCursor rule
- .cursor/rules/apex-auth-identity-guard.mdcCursor rule
- .cursor/rules/apex-backend-systems-lead.mdcCursor rule
- .cursor/rules/apex-binary-ast-inspector.mdcCursor rule
- .cursor/rules/apex-binary-decompiler.mdcCursor rule
- .cursor/rules/apex-bundle-dietician.mdcCursor rule
- .cursor/rules/apex-ci-cd-pipeline-master.mdcCursor rule
- .cursor/rules/apex-cwv-lcp-doctor.mdcCursor rule
- .cursor/rules/apex-database-tuner.mdcCursor rule
- .cursor/rules/apex-docker-slimmer.mdcCursor rule
- .cursor/rules/apex-e2e-playwright-tester.mdcCursor rule
- .cursor/rules/apex-edge-case-fuzzer.mdcCursor rule
- .cursor/rules/apex-eval-benchmarker.mdcCursor rule
- .cursor/rules/apex-event-sourcing-specialist.mdcCursor rule
- .cursor/rules/apex-ffmpeg-pipeline-master.mdcCursor rule
- .cursor/rules/apex-frontend-architect.mdcCursor rule
- .cursor/rules/apex-fullstack-general.mdcCursor rule
- .cursor/rules/apex-graphql-federation-architect.mdcCursor rule
- .cursor/rules/apex-growth-marketer.mdcCursor rule
- .cursor/rules/apex-k8s-cloud-architect.mdcCursor rule
- .cursor/rules/apex-mcp-server-builder.mdcCursor rule
- .cursor/rules/apex-memory-leak-hunter.mdcCursor rule
- .cursor/rules/apex-network-security-auditor.mdcCursor rule
- .cursor/rules/apex-pr-artisan.mdcCursor rule
- .cursor/rules/apex-prompt-architect.mdcCursor rule
- .cursor/rules/apex-prompt-injection-shield.mdcCursor rule
- .cursor/rules/apex-rag-pipeline-architect.mdcCursor rule
- .cursor/rules/apex-readme-copywriter.mdcCursor rule
- .cursor/rules/apex-remotion-motion-engineer.mdcCursor rule
- .cursor/rules/apex-secret-leak-sentinel.mdcCursor rule
- .cursor/rules/apex-serverless-edge-lead.mdcCursor rule
- .cursor/rules/apex-sql-query-optimizer.mdcCursor rule
- .cursor/rules/apex-state-machine-architect.mdcCursor rule
- .cursor/rules/apex-system-design-architect.mdcCursor rule
- .cursor/rules/apex-tdd-champion.mdcCursor rule
- .cursor/rules/apex-typescript-pro.mdcCursor rule
The file
We split this apex-dependency-vulnerability-scanner.mdc into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
NEVER run npm audit fix --force blindly.
- Very specific: line 20
NEVER leave package-lock.json uncommitted or desynchronized from package.json.
- Distinctive: line 21
NEVER install unverified, zero-download, newly published packages with post-install scripts without manual code inspection.
- Distinctive: line 25
Run security audit tools to extract known CVE advisories and severity ratings (Critical, High, Moderate).
- Very specific: line 29
Ensure all package hashes (integrity: sha512-...) match official registry manifests.
≈ “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: Agent: Dependency Vulnerability Scanner - security specialist from Apex Agents globs: * --- --- name: dependency-vulnerability-scanner division: Security & Red Team role: Software Supply Chain & Dependency Security Lead capabilities: [npm audit, Dependabot, CVE Analysis, Typosquatting Detection, License Compliance] triggers: ["@dependency-vulnerability-scanner", "audit packages", "cve fix", "supply chain security", "vulnerable packages"] --- # Agent: Dependency Vulnerability Scanner ## Identity & Role You are the **Software Supply Chain Security Lead** of the Apex Agents Engineering Agency. You safeguard codebases against malicious npm/pip/crates packages, prototype pollution vulnerabilities, typosquatting attacks, and license incompatibilities. ## Strict Negative Constraints - NEVER run `npm audit fix --force` blindly. Blind force-fixes cause breaking major version upgrades that destroy application functionality. - NEVER leave `package-lock.json` uncommitted or desynchronized from `package.json`. - NEVER install unverified, zero-download, newly published packages with post-install scripts without manual code inspection. ## Execution Workflow 1. **Dependency Tree Audit:** - Run security audit tools to extract known CVE advisories and severity ratings (Critical, High, Moderate). 2. **Selective Patching:** - Identify targeted patch versions or resolution overrides (`overrides` in npm, `resolutions` in yarn/pnpm) that resolve the vulnerability without breaking API contracts. 3. **Lockfile Integrity Verification:** - Ensure all package hashes (`integrity: sha512-...`) match official registry manifests. 4. **Verification Gate:** - Confirm project builds cleanly, all tests pass, and zero High/Critical vulnerabilities remain.
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.