Skip to content
Back to search

cyber-neo

Open-source cybersecurity analysis agent for Claude Code. Scans projects for vulnerabilities across all OWASP 2025 Top 10 and CWE Top 25 categories. 11 security domains, 60+ secret patterns, parallel subagent analysis, professional report generation. Built by tododeia.com

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hainrixz--cyber-neo/badge.svg)](/listings/hainrixz--cyber-neo)

HTML

<a href="/listings/hainrixz--cyber-neo"><img src="/api/listings/hainrixz--cyber-neo/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Option 1: Clone to Skills Directory (Recommended)

cd ~/.claude/skills
git clone https://github.com/Hainrixz/cyber-neo.git

That's it. Claude Code automatically discovers the skill.

Option 2: Symlink from Any Location

git clone https://github.com/Hainrixz/cyber-neo.git ~/projects/cyber-neo
ln -s ~/projects/cyber-neo ~/.claude/skills/cyber-neo

Option 3: Claude Code Plugin Marketplace

/plugin install cyber-neo

> *Marketplace availability coming soon.*

Verify Installation

Open Claude Code and type:

/cyber-neo

If installed correctly, Cyber Neo will ask you for a project path to scan.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/plugin.json · Manifest · 21 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "cyber-neo",
  3. "description": "Open-source cybersecurity analysis agent. Scans any local project for vulnerabilities: code security (SAST), dependency CVEs (SCA), secret leaks, authentication/authorization flaws, cryptographic weaknesses, misconfigurations, supply chain risks, and CI/CD security. Covers all OWASP 2025 Top 10 and CWE Top 25 categories. Generates prioritized reports with remediation guidance. Invoke with /cyber-neo [path].",
  4. "version": "0.1.0",
  5. "author": {
  6. "name": "mhenry"
  7. },
  8. "license": "MIT",
  9. "keywords": [
  10. "security",
  11. "cybersecurity",
  12. "SAST",
  13. "SCA",
  14. "vulnerability",
  15. "OWASP",
  16. "CWE",
  17. "audit",
  18. "secrets",
  19. "supply-chain"
  20. ]
  21. }
README.md · README · 513 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. <img src="assets/cyber-neo-hero.png" alt="Cyber Neo — Claw'd, the open-source cybersecurity mascot, holding a green padlock shield" width="820">
  3. # CYBER NEO
  4. ### The Open-Source Cybersecurity Agent for Claude Code
  5. **Protect your apps. Protect your users. Protect your community.**
  6. [![License: MIT](https://img.shields.io/badge/License-MIT-00ff41.svg)](https://opensource.org/licenses/MIT)
  7. [![OWASP 2025](https://img.shields.io/badge/OWASP-2025%20Top%2010-00ff41.svg)](https://owasp.org/www-project-top-ten/)
  8. [![CWE Top 25](https://img.shields.io/badge/CWE-Top%2025%20(2025)-00ff41.svg)](https://cwe.mitre.org/top25/)
  9. [![Claude Code](https://img.shields.io/badge/Claude%20Code-Skill-00ff41.svg)](https://claude.ai/code)
  10. [![Community](https://img.shields.io/badge/Community-tododeia.com-00ff41.svg)](https://tododeia.com)
  11. [![Instagram](https://img.shields.io/badge/Shipped%20by-@soyenriquerocha-E4405F.svg?logo=instagram&logoColor=white)](https://instagram.com/soyenriquerocha)
  12. ---
  13. *Shipped by [@soyenriquerocha](https://instagram.com/soyenriquerocha) | Built by the [Tododeia](https://tododeia.com) community — empowering developers to ship secure software.*
  14. </div>
  15. ---
  16. ## What is Cyber Neo?
  17. **Cyber Neo** is a comprehensive cybersecurity analysis agent that runs inside [Claude Code](https://claude.ai/code). Point it at any project on your computer, and it performs a deep security audit — scanning your code, dependencies, secrets, infrastructure, and supply chain for vulnerabilities. It generates a professional, prioritized report with actionable remediation guidance so you can fix issues before they become incidents.
  18. **No security expertise required.** Just run `/cyber-neo` and let the agent do the work.
  19. Cyber Neo was built with a mission: our community at [tododeia.com](https://tododeia.com) is building apps, tools, and products. We want to help every developer in the community protect what they're building. This agent is our contribution — open source, free, and designed to be the most thorough security scanner available as a Claude Code skill.
  20. ---
  21. ## Why Cyber Neo?
  22. Most security tools require installation, configuration, and expertise to interpret results. Cyber Neo is different:
  23. | Traditional Security Tools | Cyber Neo |
  24. |---|---|
  25. | Require installation and setup | Works instantly as a Claude Code skill |
  26. | Need security expertise to interpret | Plain-language findings with code-level remediation |
  27. | Scan one category (SAST *or* SCA *or* secrets) | Scans **11 categories** in one run |
  28. | Output raw findings without context | CWE/OWASP-classified findings with fix examples |
  29. | Run sequentially | **5 parallel subagents** for speed |
  30. | Require paid licenses for full coverage | **100% free and open source** |
  31. ---
  32. ## What It Scans
  33. <div align="center"><img src="assets/claw-d-scanner.png" alt="Claw'd inspecting code with a magnifying glass and spotting a bug" width="280"></div>
  34. Cyber Neo covers **11 security domains** across every major vulnerability class:
  35. | # | Category | What It Finds | How |
  36. |---|----------|--------------|-----|
  37. | 1 | **Code Security (SAST)** | SQL injection, XSS, command injection, code injection, path traversal, SSRF, deserialization, prototype pollution | Semgrep (optional) + Claude-native pattern analysis |
  38. | 2 | **Authentication & Authorization** | Missing auth middleware, JWT misconfigurations, broken access control, IDOR, session management flaws, missing RBAC | Claude-native analysis using `auth-authz-patterns.md` |
  39. | 3 | **Cryptographic Security** | Weak algorithms (MD5, SHA1, DES, RC4), hardcoded keys/IVs, TLS bypass, insecure random, weak key lengths | Claude-native analysis using `crypto-patterns.md` |
  40. | 4 | **Secret Detection** | 60+ regex patterns: AWS, GCP, Azure, GitHub, Slack, Stripe, database credentials, private keys, API keys, JWT tokens, .env files | Python batch scanner + Gitleaks (optional) |
  41. | 5 | **Dependency Vulnerabilities (SCA)** | Known CVEs in npm, pip, cargo, bundler, composer, and Go dependencies | Trivy / npm audit / pip-audit / cargo-audit (optional) |
  42. | 6 | **Web Security** | Missing security headers (CSP, CORS, HSTS), CSRF, cookie flags, file upload flaws, open redirects | Claude-native analysis using `web-security-patterns.md` |
  43. | 7 | **Supply Chain Security** | Lock file integrity, dependency confusion, typosquatting, unpinned versions, malicious packages | Python lockfile checker + Claude-native analysis |
  44. | 8 | **CI/CD Security** | GitHub Actions script injection, overly permissive permissions, unpinned actions, secret exposure in workflows | Claude-native analysis using `cicd-security.md` |
  45. | 9 | **Docker & Container Security** | Root user, unpinned base images, secrets in layers, privileged containers, Docker socket exposure | Claude-native analysis using `iac-docker.md` |
  46. | 10 | **Error Handling** | Debug mode in production, stack trace exposure, empty catch blocks, missing error boundaries | Claude-native analysis using `error-handling-patterns.md` |
  47. | 11 | **Logging Security** | Sensitive data in logs, log injection, missing security event logging | Claude-native analysis using `logging-patterns.md` |
  48. ### Standards Coverage
  49. Cyber Neo maps every finding to industry standards:
  50. - **All 10 OWASP 2025 Top 10 categories** — including the two new entries: *A03 Software Supply Chain Failures* and *A10 Mishandling of Exceptional Conditions*
  51. - **15+ CWE Top 25 (2025) items** — XSS, SQLi, CSRF, command injection, SSRF, deserialization, path traversal, missing auth, broken crypto, hardcoded credentials, and more
  52. - **CVSS-aligned severity scoring** — Critical (9.0-10.0), High (7.0-8.9), Medium (4.0-6.9), Low (1.0-3.9), Info (0.0-0.9)
  53. ---
  54. ## Supported Languages & Frameworks
  55. | Language | Frameworks | Reference File |
  56. |----------|-----------|---------------|
  57. | **JavaScript / TypeScript** | Express, Next.js, React, Vue, Angular, Fastify, NestJS, Koa, Electron | `lang-javascript.md` (924 lines) |
  58. | **Python** | Django, Flask, FastAPI, Tornado, Starlette | `lang-python.md` (935 lines) |
  59. | **Any language** | Generic SAST patterns (eval, exec, hardcoded creds, command injection) | Built into SKILL.md |
  60. > **Coming in v0.2:** Go, Ruby/Rails, Java/Spring, Rust, PHP/Laravel
  61. ---
  62. ## Installation
  63. ### Option 1: Clone to Skills Directory (Recommended)
  64. ```bash
  65. cd ~/.claude/skills
  66. git clone https://github.com/Hainrixz/cyber-neo.git
  67. ```
  68. That's it. Claude Code automatically discovers the skill.
  69. ### Option 2: Symlink from Any Location
  70. ```bash
  71. git clone https://github.com/Hainrixz/cyber-neo.git ~/projects/cyber-neo
  72. ln -s ~/projects/cyber-neo ~/.claude/skills/cyber-neo
  73. ```
  74. ### Option 3: Claude Code Plugin Marketplace
  75. ```
  76. /plugin install cyber-neo
  77. ```
  78. > *Marketplace availability coming soon.*
  79. ### Verify Installation
  80. Open Claude Code and type:
  81. ```
  82. /cyber-neo
  83. ```
  84. If installed correctly, Cyber Neo will ask you for a project path to scan.
  85. ---
  86. ## Usage
  87. ### Basic Scan
  88. ```bash
  89. # Scan a specific project
  90. /cyber-neo /path/to/your/project
  91. # Scan the current working directory
  92. /cyber-neo .
  93. ```
  94. ### What Happens When You Run It
  95. ```
  96. Phase 1: Reconnaissance
  97. Detects your tech stack, frameworks, and infrastructure
  98. Estimates project scope and applies scanning tier
  99. Phase 2-6: Parallel Analysis (5 subagents)
  100. Dependency vulnerabilities (SCA)
  101. Code security patterns (SAST)
  102. Secret detection (60+ regex patterns)
  103. Configuration & infrastructure checks
  104. Supply chain & CI/CD security
  105. Phase 7: Report Generation
  106. Deduplicates, scores, and classifies findings
  107. Generates professional security report
  108. ```
  109. ### Output
  110. The report is saved to your Desktop:
  111. ```
  112. ~/Desktop/cyber-neo-report-{project-name}-{YYYY-MM-DD}.md
  113. ```
  114. ---
  115. ## Report Format
  116. Every Cyber Neo report includes:
  117. ### Executive Summary
  118. ```markdown
  119. Risk Score: 67/100 (High Risk)
  120. | Severity | Count |
  121. |----------|-------|
  122. | Critical | 2 |
  123. | High | 5 |
  124. | Medium | 8 |
  125. | Low | 3 |
  126. | Info | 4 |
  127. Top 3 Priority Actions:
  128. 1. Fix SQL injection in src/api/users.js:42 — use parameterized queries
  129. 2. Rotate leaked AWS key in .env — key is active and exposed
  130. 3. Add authentication to /api/admin routes — currently public
  131. ```
  132. ### Detailed Findings
  133. Each finding includes:
  134. ```markdown
  135. [CN-001] SQL Injection in User Query
  136. Severity: Critical (CVSS ~9.8)
  137. CWE: CWE-89 (SQL Injection)
  138. OWASP: A05:2025 (Injection)
  139. Location: src/api/users.js:42
  140. Description: User input is directly concatenated into SQL query
  141. without parameterization, enabling SQL injection attacks.
  142. Evidence:
  143. const query = `SELECT * FROM users WHERE id = ${req.params.id}`;
  144. Remediation:
  145. const query = 'SELECT * FROM users WHERE id = $1';
  146. const result = await db.query(query, [req.params.id]);
  147. ```
  148. ### Additional Sections
  149. - **Dependency Vulnerabilities** — Table of CVEs with package names, versions, and fix versions
  150. - **Supply Chain Assessment** — Lock file status, dependency pinning, CI/CD pipeline security
  151. - **Scan Metadata** — Files scanned, coverage percentage, tools used, scan duration
  152. ---
  153. ## How It Works — Architecture Deep Dive
  154. <div align="center"><img src="assets/claw-d-architecture.png" alt="Claw'd analyzing code on a terminal showing a passing check" width="280"></div>
  155. Cyber Neo is built as a Claude Code **skill** — a markdown-based prompt that orchestrates Claude's analysis capabilities. The architecture has three layers:
  156. ### Layer 1: SKILL.md — The Orchestration Engine
  157. The `SKILL.md` file (563 lines) is the brain of Cyber Neo. It contains:
  158. - **7-phase analysis pipeline** with explicit instructions for each phase
  159. - **Subagent dispatch templates** for parallel analysis
  160. - **Severity scoring rubric** aligned with CVSS
  161. - **Report generation instructions** with deduplication and classification rules
  162. - **Safety constraints** (read-only iron law) reinforced in every subagent prompt
  163. - **Edge case handling** for empty projects, unsupported languages, and large codebases
  164. ### Layer 2: Reference Files — The Security Knowledge Base
  165. 14 reference files totaling **10,000+ lines** of security patterns:
  166. ```
  167. references/
  168. ├── owasp-top-10.md # OWASP 2025 classification + scoring guide
  169. ├── cwe-top-25.md # CWE mappings with detection patterns
  170. ├── secrets-patterns.md # 60+ regex patterns for secret detection
  171. ├── auth-authz-patterns.md # JWT, sessions, RBAC, IDOR patterns
  172. ├── crypto-patterns.md # Weak crypto, hardcoded keys, TLS bypass
  173. ├── web-security-patterns.md # Headers, CORS, CSRF, SSRF, uploads, redirects
  174. ├── error-handling-patterns.md # Debug mode, stack traces, empty catches
  175. ├── logging-patterns.md # Sensitive data in logs, log injection
  176. ├── cicd-security.md # GitHub Actions injection, permissions
  177. ├── supply-chain.md # Dependency confusion, typosquatting, lock files
  178. ├── lang-javascript.md # Node/Express/Next.js/React patterns (924 lines)
  179. ├── lang-python.md # Django/Flask/FastAPI patterns (935 lines)
  180. ├── iac-docker.md # Dockerfile/Compose security (1,005 lines)
  181. └── report-template.md # Report format specification
  182. ```
  183. Each reference file contains:
  184. - **Grep-ready regex patterns** Claude can use for analysis
  185. - **Vulnerable code examples** showing the actual problem
  186. - **Secure code examples** showing the fix
  187. - **CWE and OWASP 2025 mappings** for classification
  188. - **Severity ratings** for consistent scoring
  189. ### Layer 3: Python Scripts — Batch Processing
  190. Two Python scripts handle tasks where batch processing is faster than sequential Claude analysis:
  191. | Script | Purpose | Lines |
  192. |--------|---------|-------|
  193. | `scan_secrets.py` | Regex-based secret scanning across all files. 60+ patterns covering AWS, GCP, GitHub, Slack, Stripe, database credentials, private keys, API keys, and more. Includes smart allowlisting to reduce false positives. | 510 |
  194. | `check_lockfiles.py` | Lock file integrity verification for 10 package managers (npm, yarn, pnpm, bun, pip, pipenv, poetry, cargo, bundler, composer, Go). Detects missing lock files, unpinned dependencies, and risky lifecycle scripts. | 340 |
  195. Both scripts:
  196. - Use **only Python standard library** (zero dependencies)
  197. - Output **structured JSON** for easy parsing
  198. - Handle edge cases gracefully (empty dirs, missing files, binary files)
  199. - Are strictly **read-only** — never modify the target project
  200. ---
  201. ## Optional: External Tool Integration
  202. Cyber Neo works **out of the box** using Claude-native analysis. For deeper scanning, install these optional tools:
  203. | Tool | Category | Install | What It Adds |
  204. |------|----------|---------|-------------|
  205. | [Semgrep](https://semgrep.dev) | SAST | `brew install semgrep` | 3,000+ community rules for 30+ languages |
  206. | [Trivy](https://trivy.dev) | SCA | `brew install trivy` | Comprehensive dependency vulnerability database |
  207. | [Gitleaks](https://gitleaks.io) | Secrets | `brew install gitleaks` | Git history scanning for committed secrets |
  208. | [pip-audit](https://pypi.org/project/pip-audit/) | Python SCA | `pip install pip-audit` | Python package vulnerability checking |
  209. | [cargo-audit](https://crates.io/crates/cargo-audit) | Rust SCA | `cargo install cargo-audit` | Rust crate vulnerability checking |
  210. When these tools are installed, Cyber Neo automatically detects and uses them alongside its built-in analysis for deeper coverage.
  211. ---
  212. ## Scope Tiering — How It Handles Large Projects
  213. Cyber Neo adapts its scanning strategy based on project size:
  214. | Tier | File Count | Strategy |
  215. |------|-----------|----------|
  216. | **Small** | < 1,000 | Full scan — every source file analyzed |
  217. | **Medium** | 1,000 - 10,000 | Targeted scan — prioritizes `src/`, `app/`, API routes, auth middleware, config files |
  218. | **Large** | 10,000+ | Critical-path scan — focuses on entry points, auth, config, deps. Reports coverage percentage |
  219. The final report always shows how many files were scanned vs. skipped, so you know exactly what was covered.
  220. ---
  221. ## Safety Guarantees
  222. <div align="center"><img src="assets/claw-d-shield.png" alt="Claw'd standing guard behind a shield with a green padlock — the read-only iron law" width="280"></div>
  223. Cyber Neo follows a strict **read-only iron law**:
  224. | Rule | Description |
  225. |------|-------------|
  226. | **Never modifies files** | Your project files are never changed, deleted, or created |
  227. | **Never executes code** | No `npm start`, `python app.py`, or any project execution |
  228. | **Never installs packages** | No `npm install`, `pip install`, or dependency modifications |
  229. | **Never runs fix commands** | No `npm audit --fix` or auto-remediation |
  230. | **Single write operation** | Only writes the report file to `~/Desktop/` |
  231. | **Secrets are redacted** | Detected secrets are never included in the report |
  232. These constraints are enforced at the top level AND in every subagent prompt.
  233. ---
  234. ## OWASP 2025 Top 10 Coverage Map
  235. | ID | Category | Where Addressed |
  236. |----|----------|----------------|
  237. | A01:2025 | Broken Access Control | `auth-authz-patterns.md` — missing middleware, IDOR, privilege escalation |
  238. | A02:2025 | Security Misconfiguration | `web-security-patterns.md` + `error-handling-patterns.md` — headers, debug mode, env config |
  239. | A03:2025 | Software Supply Chain Failures | `supply-chain.md` + `cicd-security.md` — dep confusion, typosquatting, CI injection |
  240. | A04:2025 | Cryptographic Failures | `crypto-patterns.md` + `secrets-patterns.md` — weak algorithms, hardcoded keys |
  241. | A05:2025 | Injection | `lang-javascript.md` + `lang-python.md` + `web-security-patterns.md` — SQLi, XSS, SSRF |
  242. | A06:2025 | Insecure Design | `auth-authz-patterns.md` + `web-security-patterns.md` — structural design flaws |
  243. | A07:2025 | Authentication Failures | `auth-authz-patterns.md` — JWT, sessions, password hashing, OAuth |
  244. | A08:2025 | Software/Data Integrity Failures | `lang-*.md` + `supply-chain.md` — deserialization, dependency integrity |
  245. | A09:2025 | Logging/Monitoring Failures | `logging-patterns.md` — sensitive data in logs, missing security logging |
  246. | A10:2025 | Mishandling of Exceptional Conditions | `error-handling-patterns.md` — empty catches, stack traces, debug mode |
  247. ---
  248. ## Remediation Workflow
  249. After running Cyber Neo, we recommend a **test-driven security fix** approach:
  250. ```
  251. 1. Read the report — start with Critical findings
  252. 2. Pick the highest-severity finding
  253. 3. Write a test that proves the vulnerability exists
  254. 4. Apply the fix from the remediation guidance
  255. 5. Run the test — verify it passes
  256. 6. Re-run /cyber-neo to confirm the finding is resolved
  257. 7. Repeat for the next finding
  258. ```
  259. If you have the [Superpowers](https://github.com/obra/superpowers) plugin installed, use its TDD workflow for structured remediation.
  260. ---
  261. ## Skill Integration
  262. Cyber Neo works with other Claude Code skills for enhanced analysis:
  263. | Skill | Integration |
  264. |-------|------------|
  265. | [/last30days](https://github.com/mvanhorn/last30days-skill) | Researches emerging threats and community discussions about your detected stack |
  266. | /deep-research | Looks up context on unfamiliar CVEs or emerging threats found during scan |
  267. | [Superpowers](https://github.com/obra/superpowers) | TDD-driven remediation workflow for fixing findings systematically |
  268. ---
  269. ## Project Structure
  270. ```
  271. cyber-neo/
  272. ├── .claude-plugin/
  273. │ └── plugin.json # Plugin metadata
  274. ├── skills/
  275. │ └── cyber-neo/
  276. │ ├── SKILL.md # Orchestration engine (563 lines)
  277. │ ├── scripts/
  278. │ │ ├── scan_secrets.py # Batch secret scanner (510 lines)
  279. │ │ └── check_lockfiles.py # Lock file checker (340 lines)
  280. │ └── references/ # Security knowledge base (14 files, 10K+ lines)
  281. │ ├── owasp-top-10.md
  282. │ ├── cwe-top-25.md
  283. │ ├── secrets-patterns.md
  284. │ ├── auth-authz-patterns.md
  285. │ ├── crypto-patterns.md
  286. │ ├── web-security-patterns.md
  287. │ ├── error-handling-patterns.md
  288. │ ├── logging-patterns.md
  289. │ ├── cicd-security.md
  290. │ ├── supply-chain.md
  291. │ ├── lang-javascript.md
  292. │ ├── lang-python.md
  293. │ ├── iac-docker.md
  294. │ └── report-template.md
  295. ├── CLAUDE.md # Contributor guidelines
  296. ├── LICENSE # MIT
  297. └── README.md # This file
  298. ```
  299. ---
  300. ## Roadmap
  301. ### v0.1.0 (Current)
  302. - 7-phase analysis pipeline with parallel subagents
  303. - JavaScript/TypeScript + Python language support
  304. - 14 security reference files (10,000+ lines)
  305. - 60+ secret detection patterns
  306. - 10 package manager support for lock file checks
  307. - Full OWASP 2025 Top 10 and CWE Top 25 coverage
  308. - Professional report generation with CWE/OWASP mapping
  309. ### v0.2.0 (Planned)
  310. - Go, Ruby/Rails, Java/Spring, Rust language patterns
  311. - Kubernetes and Terraform/IaC security scanning
  312. - OWASP Top 10 for LLMs (prompt injection, sensitive data in AI apps)
  313. - Mobile security patterns (React Native, Flutter)
  314. - Serverless/Lambda security patterns
  315. - GraphQL security analysis
  316. - SARIF output format for CI/CD integration
  317. - Configuration sub-skill (`/cyber-neo:config`)
  318. ### v0.3.0 (Future)
  319. - Session-start hook for automatic security context
  320. - ASVS (Application Security Verification Standard) mapping
  321. - Trend tracking (re-scan and diff findings over time)
  322. - Cross-platform support (Cursor, Copilot CLI, Windsurf)
  323. - CI/CD integration mode (GitHub Action wrapper)
  324. - Race condition detection patterns
  325. ---
  326. ## Contributing
  327. We welcome contributions from the community. See [CLAUDE.md](CLAUDE.md) for detailed contributor guidelines.
  328. ### Key Principles
  329. 1. **SKILL.md is the product** — its quality determines how good the agent is
  330. 2. **Reference files are pure knowledge** — grep-ready patterns with CWE/OWASP mappings
  331. 3. **Scripts use only standard library** — zero pip dependencies
  332. 4. **Every finding needs classification** — CWE ID, OWASP category, severity, and remediation
  333. 5. **Read-only on target projects** — never modify what we're scanning
  334. ### How to Add a New Language
  335. 1. Create `references/lang-{language}.md` following the existing pattern
  336. 2. Add framework detection patterns, vulnerability patterns with grep regex, and secure/vulnerable code examples
  337. 3. Map every pattern to CWE and OWASP 2025 categories
  338. 4. Update SKILL.md Phase 1.1 to detect the new language
  339. 5. Update SKILL.md Phase 1.3 to load the new reference file
  340. 6. Test against a deliberately vulnerable project in that language
  341. ---
  342. ## Community
  343. <div align="center"><img src="assets/claw-d-community.png" alt="Claw'd waving and holding up an A+ security report" width="280"></div>
  344. Cyber Neo is shipped by **[@soyenriquerocha](https://instagram.com/soyenriquerocha)** and built by the **[Tododeia](https://tododeia.com)** community — a growing network of developers building apps, tools, and products together. We believe every developer deserves access to enterprise-grade security tooling, for free.
  345. - **Creator:** [@soyenriquerocha](https://instagram.com/soyenriquerocha) on Instagram
  346. - **Community:** [tododeia.com](https://tododeia.com)
  347. - **GitHub:** [github.com/Hainrixz/cyber-neo](https://github.com/Hainrixz/cyber-neo)
  348. - **License:** MIT — use it, modify it, share it
  349. ---
  350. ## Acknowledgments
  351. Cyber Neo builds on the shoulders of the security community:
  352. - [OWASP Foundation](https://owasp.org) — Top 10 and ASVS standards
  353. - [MITRE](https://cwe.mitre.org) — CWE vulnerability classification
  354. - [Semgrep](https://semgrep.dev) — Static analysis patterns and rules
  355. - [Trivy](https://trivy.dev) — Vulnerability database
  356. - [Superpowers](https://github.com/obra/superpowers) — Skill architecture patterns
  357. - [last30days](https://github.com/mvanhorn/last30days-skill) — Research integration patterns
  358. ---
  359. <div align="center">
  360. **Shipped by [@soyenriquerocha](https://instagram.com/soyenriquerocha) | Built with purpose. Open source forever.**
  361. *Protecting the apps our community builds — one scan at a time.*
  362. [Get Started](#installation) | [Report an Issue](https://github.com/Hainrixz/cyber-neo/issues) | [Join the Community](https://tododeia.com) | [Follow @soyenriquerocha](https://instagram.com/soyenriquerocha)
  363. </div>
  364. <!-- marca-agua:inicio -->
  365. ---
  366. <sub>Hecho por **Enrique Rocha (@soyenriquerocha)** · [tododeia.com](https://www.tododeia.com)⁠​‌‌​​‌​‌​‌‌‌​​‌​​​‌​‌‌​‌​‌‌​​‌​​​​‌‌​‌​‌​‌‌​​‌​‌​​‌‌​‌‌​​‌‌​​‌​‌​​‌‌‌​​​​‌‌​​​‌​​​‌‌​​​‌⁠</sub>
  367. <!-- marca-agua:fin -->

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.