agentleFS
skyelan1999skyelan1999/aide/.agents/skills/aide-security/SKILL.md

aide-security

Skill4 starsChanged 31 days agoMITView on GitHub

Review or implement Aide authentication, permissions, tokens, secrets, path safety, encryption, or other security-sensitive behavior.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Add focused positive and negative-path regression coverage.

    line 10

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

Aide security-sensitive changes

  • Trace the server-side enforcement path; a hidden control or client-side check is not authorization. Consult docs/security/ and the relevant source before changing policy.
  • Preserve least privilege, same-origin/token checks, path containment, secret redaction, and encrypted-at-rest behavior. Treat logs, fixtures, and browser storage as potential disclosure paths.
  • Add focused positive and negative-path regression coverage. Do not use real credentials or live production data. State the threat boundary and any behavior not exercised.
  • Coordinate interface changes with backend/frontend owners; security-sensitive edits need coordinator review before integration.

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.