cybersec

Solid

Security audit toolkit for the ccboard project (Rust/Leptos/Axum stack). Use when auditing authentication flows, API endpoints, WASM security, or reviewing Rust code for unsafe usage and memory safety issues.

API & Backend 91 stars 6 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
65
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
40
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Cybersec Skills — ccboard Security audit toolkit for the ccboard Rust/Leptos stack. ## Reference files in this directory These files are reference documentation for security test patterns. Update them to reflect ccboard's actual Axum routes, auth flows, and data model. ## Key security areas for ccboard - **Authentication**: session tokens, CSRF protection in Leptos forms - **Authorization**: route-level guards in Axum middleware - **WASM**: client-side code exposure, sensitive data in WASM binary - **SQL**: raw query usage, input sanitization - **Dependency audit**: `cargo audit` for known CVEs in dependencies ## Usage ```bash cargo audit # CVE scan grep -r "unsafe" src/ # unsafe block audit grep -r "unwrap()" src/ | wc -l # panic surface audit ```

Details

Author
FlorianBruniaux
Repository
FlorianBruniaux/ccboard
Created
6 months ago
Last Updated
1 weeks ago
Language
Rust
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

mkcso

Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification. Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep scan, 2/10 bar). Trend tracking across audit runs. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review".

14 Updated 3 weeks ago
ngocsangyem
Code & Development Listed

cybersecurity

Run a defensive security review by fanning a target out across a multi-model ensemble (organizer + worker/decision tier) and consolidating the findings. Use this whenever the user wants a security audit, vulnerability review, secure code review, PR/diff security pass, infrastructure or config hardening review, dependency / supply-chain audit, threat model, or incident triage — on code, infrastructure, or systems they own or are explicitly authorized to test. Trigger it even when the user just says things like "is this safe", "review this for vulns", "harden this", "what could go wrong with this design", or "check these deps" without using the word "security". Also trigger when the user invokes /cybersecurity (or /security). Do NOT use this to produce weaponized exploit code, malware, or to attack systems the user does not control — it identifies, assesses, and remediates, it does not weaponize.

0 Updated 5 days ago
7cubit
AI & Automation Listed

security-audit

Security review for code touching authentication, credentials, file access, or user data. Includes CWE checklist ranked by AI vulnerability frequency, phantom package detection, ASVS-aligned controls, and supply chain checks. MANDATORY for auth code, credential handling, file operations with user data, network comms, or database queries with user input.

4 Updated today
joris887