session-cookie-security
Skill15 starsChanged 5 months agoCC0-1.0View on GitHub
Analyzes session and cookie security, including flags, expiration, fixation, and storage. Use when auditing session management and cookie configuration.
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 14
If no target path is given above, review the entire codebase.
- Distinctive: line 31
All cookies have appropriate flags
- Distinctive: line 32
No sensitive data in cookies
- Distinctive: line 42
Not using default in-memory storage in production
- Distinctive: line 64
Prefer minimal, drop-in fix snippets over prose.
- Distinctive: line 66
Do not invent files or functions that aren’t present.
- Distinctive: line 68
Write this into a markdown file and place it in the audits/ folder.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Session and Cookie Security
Analyze this project's source code. Focus on session management and cookie security.
Verify:
- Session configuration
- Secure flag (HTTPS only)
- HttpOnly flag (no JS access)
- SameSite attribute
- Session timeout
- Session regeneration after login
- Cookie security
- All cookies have appropriate flags
- No sensitive data in cookies
- Proper domain/path scoping
- Encryption for sensitive cookies
- CSRF Protection
- Token implementation
- Double submit cookie pattern
- Origin header validation
- Session storage
- Not using default in-memory storage in production
- Redis/database backed sessions
- Session cleanup/expiration
Provide:
A structured finding report with the following for each issue:
Title, Severity (Critical/High/Medium/Low), CWE (if applicable), Evidence (file, function, line ranges), and a short Why it matters.
Exploitability notes and, where safe, a minimal PoC or reproduction steps (no real secrets).
Remediation: precise code-level fix or config change (snippets welcome), plus defense-in-depth guidance.
A summary risk score (0–10) and top 3–5 prioritized fixes that reduce risk fastest.
A checklist diff: which items from the “Check for” list are Pass/Fail/Not Applicable.
Constraints & style:
Be concrete and cite exact code locations and identifiers.
Prefer minimal, drop-in fix snippets over prose.
Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.
Write this into a markdown file and place it in the audits/ folder.
In this repository21 other files it gives its agents.
- api-and-infrastructureSkill
- authentication-flow-reviewSkill
- authorization-implementationSkill
- business-logic-vulnerabilitiesSkill
- code-duplication-detectionSkill
- code-quality-metrics-standardsSkill
- comprehensive-security-reportSkill
- database-securitySkill
- design-pattern-implementationSkill
- error-handling-resilienceSkill
- exception-flow-analysisSkill
- file-handling-business-logicSkill
- initial-security-analysisSkill
- initial-software-design-analysisSkill
- input-validationSkill
- logging-monitoringSkill
- readability-and-namingSkill
- resilience-fault-toleranceSkill
- secrets-management-auditSkill
- solid-principlesSkill
- testing-implementationSkill
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.