agentleFS
UwayxtUwayxt/agent-skills/.agents/skills/security-privacy-review/SKILL.md

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

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
  1. Distinctive:

    Verify that sensitive areas have clear session handling:

    line 9
  2. Very specific:

    Print / Screenshot safety: Ensure sensitive account identifiers are truncated (•••• 4242) in exportable views and receipts.

    line 18
  3. Very specific:

    URL parameters: Verify no authentication tokens, emails, or sensitive IDs are exposed in query strings (?token=...).

    line 19
  4. Distinctive:

    Ensure unauthorized actions are either gracefully disabled with an explanatory tooltip or hidden entirely.

    line 22
  5. Distinctive:

    Never display a generic "403 Forbidden" page after a user clicks a visible button.

    line 23

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.