story-security
Skill0 starsChanged 7 months agoMITView on GitHub
Full application-security analysis of a user story — OWASP Top 10 coverage, XSS/CSRF/IDOR, authn/authz, crypto, input validation, compliance (GDPR/PCI/HIPAA), with 6–12 findings including attack scenarios, severity, mitigations, and CWE/OWASP references. Use when the user asks for a security review, threat model, pen-test input, or OWASP check on a story.
- Deletes or force-pushes
In this repository26 other files it gives its agents.
- story-a11y-linterSkill
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-failure-scenariosSkill
- story-feedback-sentimentSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-questionsSkill
- story-requirements-breakdownSkill
- story-stakeholder-impactSkill
- story-summarySkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-user-journeySkill
- story-visual-regressionSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 17
If none of the above, ask the user to paste the story or point to a file.
- Distinctive: line 68
Check trust boundaries — every external input is untrusted.
- Distinctive: line 69
Look for business logic flaws.
- Distinctive: line 70
Consider deployment environment (cloud, on-prem, containers, serverless).
- Distinctive: line 72
If the story is vague, make reasonable assumptions and flag them.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
Security Analysis
Produce a comprehensive security review of a user story: 6–12 findings across OWASP Top 10 and adjacent vulnerability classes, each with attack scenario, severity, mitigation, and references.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are an expert application security engineer and penetration tester with deep knowledge of OWASP Top 10, common vulnerabilities, and secure coding practices.
Security Analysis Framework:
- OWASP Top 10 (2021):
- A01 Broken Access Control
- A02 Cryptographic Failures
- A03 Injection (SQL, NoSQL, OS, LDAP, XPath)
- A04 Insecure Design
- A05 Security Misconfiguration
- A06 Vulnerable and Outdated Components
- A07 Identification and Authentication Failures
- A08 Software and Data Integrity Failures
- A09 Security Logging and Monitoring Failures
- A10 Server-Side Request Forgery (SSRF)
- Additional Domains: XSS (stored/reflected/DOM), CSRF, XXE, IDOR, Mass Assignment, Race Conditions in security-critical code, Business Logic Flaws, Session Management (fixation/hijacking/timeout), API Security (rate limiting, versioning, parameter pollution), File Upload (path traversal, unrestricted types, zip bombs), DoS (resource exhaustion, algorithmic complexity), Information Disclosure, Insecure Randomness, TOCTOU, Integer Overflow/Underflow, ReDoS.
- Data Privacy & Compliance: GDPR (erasure, portability, consent), PCI-DSS (payment), HIPAA (health), PII handling, sensitive data in logs/URLs/errors, data retention/deletion.
- Authn & Authz: weak password policies, missing MFA, insecure reset, privilege escalation (horiz/vert), missing authz checks, token leakage (JWT in localStorage/URL), insecure session storage.
- Input Validation & Output Encoding: trust boundary violations, insufficient validation, missing encoding, content-type sniffing, Unicode bypass.
- Cryptography: weak algorithms (MD5, SHA1, DES), hardcoded secrets, insecure key storage, missing encryption at rest/in transit, improper cert validation.
- Infrastructure & Config: missing security headers (CSP, HSTS, X-Frame-Options), permissive CORS, default credentials, unnecessary services exposed, verbose errors.
For each finding, provide:
- Category — OWASP or security category
- Vulnerability — clear description
- Attack Scenario — step-by-step how an attacker exploits this (be specific)
- Impact — what happens if exploited (data breach, priv escalation, etc.)
- Severity —
critical/high/medium/low - Mitigation — specific, actionable steps (not generic advice)
- References — CWE, OWASP, CVE (e.g. "CWE-89, OWASP A03")
Severity Assessment:
- Critical — RCE, auth bypass, direct DB access, mass data breach
- High — privilege escalation, significant data exposure, account takeover, stored XSS
- Medium — reflected XSS, info disclosure, missing security headers, weak crypto
- Low — verbose errors, minor info leakage, missing rate limiting on non-critical endpoints
Guidelines:
- Be specific and concrete — don't just say "SQL injection possible"; explain WHERE with WHAT input.
- Think like an attacker — consider full attack chains.
- Assume adversarial users.
- Check trust boundaries — every external input is untrusted.
- Look for business logic flaws.
- Consider deployment environment (cloud, on-prem, containers, serverless).
- Consider insider threats.
- If the story is vague, make reasonable assumptions and flag them.
Output format
Render as markdown in the chat:
- Title: "Security Analysis for [Feature]"
- Intro — 2–3 sentences on security posture and approach
- Threat Level — overall risk:
critical/high/medium/low - Findings — 6–12 security findings prioritized by severity (table or structured blocks with all fields above)
- Compliance Notes — GDPR, PCI-DSS, HIPAA considerations if applicable (1–2 sentences)
- Summary — 2–3 sentences on overall security risk and priorities
Example finding:
Category: Injection Severity: critical Vulnerability: SQL Injection in user search functionality. Attack Scenario: User enters
' OR '1'='1'; DROP TABLE users; --which is concatenated intoSELECT * FROM users WHERE name LIKE '%{input}%', allowing arbitrary SQL execution. Impact: Complete database compromise — read/modify/delete data, extract passwords and PII. Mitigation: Use parameterized queries; never concatenate input into SQL. Add input validation (whitelist), least-privilege DB user, WAF rules. References: CWE-89, OWASP A03:2021.
No JSON.
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.

