agentleFS
Sign inStart free
DongDuong2001DongDuong2001/pudo-code-system/skills/plan/security/SKILL.md

security-plan

Skill5 starsChanged 5 months agoMITView on GitHub

Threat modeling, compliance, and secure by design architecture

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

    When performing Threat Modeling (STRIDE) for new features.

    line 11
  2. Distinctive:

    When planning Authentication, Authorization, and Session Management.

    line 12
  3. Distinctive:

    When adhering to compliance requirements (GDPR, HIPAA, SOC2).

    line 13
  4. Distinctive:

    Defense in Depth: Do not rely on a single defensive mechanism.

    line 17
  5. Distinctive:

    Secret Management: Never hardcode secrets. Plan to use KMS, HashiCorp Vault, or environment-injected managed identities.

    line 18

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

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

Security Planning Skill

This skill is focused on ensuring systems are resilient against attacks and inherently protect user data.

When to use this skill

  • When performing Threat Modeling (STRIDE) for new features.
  • When planning Authentication, Authorization, and Session Management.
  • When adhering to compliance requirements (GDPR, HIPAA, SOC2).

Guidelines

  • Principle of Least Privilege: Services and users should only have the bare minimum access permissions they need.
  • Defense in Depth: Do not rely on a single defensive mechanism. Validate inputs at the client, the API edge, and the database boundary.
  • Secret Management: Never hardcode secrets. Plan to use KMS, HashiCorp Vault, or environment-injected managed identities.

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.

Reviews can't be read right now.

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.

Check your setup, free