security-privacy-review
Skill4 starsChanged 3 months agoMITView on GitHub
Audit interface for auth boundaries, sensitive data exposure, and privacy compliance. Use when security review, privacy audit, data exposure, GDPR, or auth UX.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Xakki/ai-agents-skillstheir own version, first seen Nov 8, 2026
- dathuynh1108/agent-skillstheir own version, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Xakki/ai-agents-skills★ 6same name
- dathuynh1108/agent-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Verify that sensitive areas have clear session handling:
- Very specific: line 18
Print / Screenshot safety: Ensure sensitive account identifiers are truncated (•••• 4242) in exportable views and receipts.
- Very specific: line 19
URL parameters: Verify no authentication tokens, emails, or sensitive IDs are exposed in query strings (?token=...).
- Distinctive: line 22
Ensure unauthorized actions are either gracefully disabled with an explanatory tooltip or hidden entirely.
- Distinctive: line 23
Never display a generic "403 Forbidden" page after a user clicks a visible button.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 and privacy in product design are not back-end checkboxes — they are visual boundaries that prevent accidental data leaks, clarify consent, and protect user trust.
1. Audit authentication and session lifecycle UX
Verify that sensitive areas have clear session handling:
- Session expiration: Modal warning prior to logout ("Your session expires in 2 minutes") with seamless renew action.
- Sensitive actions re-authentication: High-risk actions (changing password, deleting account, exporting customer data) require password or 2FA confirmation modal.
- Remember-me clarity: Clearly communicate session duration implications on shared devices.
2. Prevent UI data exposure & PII leakage
Audit screens for accidental exposure of Personally Identifiable Information (PII) and credentials:
- Masking: Passwords, API keys, credit card numbers, and secret tokens must be masked by default with explicit "Reveal" eye-icon toggles.
- Copy-to-clipboard feedback: Confirm copied items without echoing unmasked secrets in toast notifications.
- Print / Screenshot safety: Ensure sensitive account identifiers are truncated (
•••• 4242) in exportable views and receipts. - URL parameters: Verify no authentication tokens, emails, or sensitive IDs are exposed in query strings (
?token=...).
3. Review role-based permission boundaries (RBAC)
- Ensure unauthorized actions are either gracefully disabled with an explanatory tooltip or hidden entirely.
- Never display a generic "403 Forbidden" page after a user clicks a visible button; prevent dead ends by reflecting permission limits in navigation and button states.
4. Verify privacy, consent, and GDPR compliance flows
- Consent checkboxes: Explicit opt-in (never pre-checked) for marketing communications and analytics cookies.
- Data deletion & export: Clear, accessible user paths to export personal data (JSON/CSV) and request account deletion with transparent confirmation warnings.
- Destructive action safeguards: Red destructive buttons with explicit confirmation inputs (e.g. typing workspace name "my-workspace" to delete).
Completion Criteria
- Session expiry and re-authentication touchpoints designed
- PII, credentials, and API keys masked by default with safe reveal mechanisms
- No sensitive credentials exposed in URL query parameters
- Role-based action boundaries reflected gracefully in UI states
- Consent opt-in, data export, and destructive deletion flows verified
Output
A security-privacy-audit.md listing potential data exposure risks, permission boundary violations, and actionable design remediation tasks.
Anti-patterns
- Pre-checked consent boxes for terms or data sharing.
- Unmasked API keys or secrets displayed in plain text by default.
- Generic 403 / 401 error screens on primary navigation paths.
- Permanent data deletion executed with a single unverified click.
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.

