Skip to content
Skills Library
Security · Review & audit

secure

/secure

Security audit. Triggers on /codeforge:secure or code touching auth, inputs, APIs, payments, secrets. OWASP Top 10 plus supply chain.

Repository
codeforge ↗
Licence
MIT
Last repository change
26.06.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Security audit. Triggers on /codeforge:secure or code touching auth, inputs, APIs, payments, secrets. OWASP Top 10 plus supply chain.

Original author description

Security audit. Triggers on /codeforge:secure or code touching auth, inputs, APIs, payments, secrets. OWASP Top 10 plus supply chain.

How it works

  1. Threat model (state before scanning)
  2. Scan checklist
  3. Output
Original SKILL.md headings · 31 lines, 157 words
SKILL.md preview
---
name: secure
description: Security audit. Triggers on /codeforge:secure or code touching auth, inputs, APIs, payments, secrets. OWASP Top 10 plus supply chain.
allowed-tools: Read, Grep, Glob, Bash(npm audit:*), Bash(pip-audit:*)
---

# codeforge:secure

## Threat model (state before scanning)
1. Assets at risk  2. Trust boundaries  3. Likely attacker

## Scan checklist

| Class | Signal |
|-------|--------|
| Secrets | sk-, AKIA, BEGIN PRIVATE KEY, password= in source |
| SQLi | String concat in queries, raw db.query with user input |
| CMDi | exec( or subprocess with user input |
| Path traversal | ../ in file ops, unvalidated upload paths |
| Auth | IDOR no ownership check, JWT alg:none, insecure cookies |
| Crypto | MD5/SHA1 for passwords, ECB mode, Math.random for tokens |
| Input | No schema at API boundary, file upload no type+size check |
| Supply chain | Unpinned deps, open npm audit / pip-audit vulns |
| Headers | Missing CSP, HSTS, X-Frame-Options |

## Output

```
[CRITICAL|HIGH|MEDIUM|LOW] Class - Title
File: path:line
Impact: what attacker achieves
Fix: concrete remediation

Remediation order: 1. highest impact  2. ...
```
Files in this package (2)
  • SKILL.md 1 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · prashantxo/codeforge95MIT
asmn-96/ai-agents-skills-toolkit100MIT
nazmirket/skills90MIT

Database snapshot: 13.11.2026 · package version 6c117ae88c5a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100audit-security
    Perform a security audit when the user asks to check for vulnerabilities, audit security, review OWASP compliance, scan for secrets, or assess application security posture
  • 95security-audit
    [Code Quality] Use when a workflow step or the user asks for security audits: OWASP, secrets, supply chain, infrastructure, CI/CD and AI-agent risks.
  • 95security-audit
    [Code Quality] Use when a workflow step or the user asks for security audits: OWASP, secrets, supply chain, infrastructure, CI/CD and AI-agent risks.
  • 90secure-engineering
    Apply threat-boundary analysis and scoped security checks to auth, input, secrets, sensitive data, migrations, APIs, dependencies, and CI. Use when those triggers are present; do not use as a generic checklist for unrelated low-risk changes.
  • 100secure-coding
    Secure-coding discipline mapped to the OWASP Top 10, checked at the point of writing code, not after. Covers input validation and injection classes, broken access control, secrets handling, dependency/supply-chain risk, and safe error handling/logging. Use when writing code that…
  • 96ditz-secure
    Use when adding auth, secrets, or handling user input.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.