agentleFS
lukashouthoofdlukashouthoofd/cenekathon/.agents/skills/security-basics/SKILL.md

security-basics

Skill1 starsChanged 13 days agoMITView on GitHub

Use before deploying or pitching, and whenever handling API keys, user input, uploads, auth or personal data — a quick pass on the mistakes that actually bite at hackathons.

  • Reads credentials
  • Installs packages

3 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

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Access: if there's a login, check authorization on the server for every data read (not just hiding buttons).

    line 12
  2. Distinctive:

    Privacy: use synthetic or public data in the demo.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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 basics (10-minute pass)

  1. Secrets: nothing in git. git grep -nIE "sk-|api[_-]?key|secret|token|BEGIN .*PRIVATE"; check git log -p if a key was ever committed → rotate it, deleting the line isn't enough. .env ignored, .env.example complete. Keys live server-side; NEXT_PUBLIC_* / client code is public.
  2. Shared AI tokens from the organisers: don't paste them in chat, issues, screenshots or the demo recording.
  3. Input: validate server-side; parameterized SQL; escape or sanitize anything rendered as HTML (LLM output counts as untrusted); limit upload size and type.
  4. LLM-specific: user text and retrieved documents can contain prompt injection — never let model output trigger destructive actions or run as code/shell without a human check; don't put secrets in system prompts.
  5. Access: if there's a login, check authorization on the server for every data read (not just hiding buttons). Hosted DB: RLS on, service-role key never in the browser.
  6. Rate/cost guard: cap tokens per request and requests per IP/session on public AI endpoints so the shared budget survives the pitch.
  7. Privacy: use synthetic or public data in the demo; no real personal data in prompts, fixtures or screenshots.
  8. Dependencies: install only packages you've heard of; check the exact name (typosquats, hallucinated packages) — npm view <pkg> / pip index versions <pkg>.
  9. Deploy: HTTPS only (hosts do this), no debug mode in production, no verbose errors to users.
  10. Aikido: .github/workflows/aikido.yml scans every PR for new critical dependency vulnerabilities. Needs AIKIDO_SECRET_KEY (gh secret set AIKIDO_SECRET_KEY); skipped until set. Optional: Aikido Safe Chain (npm i -g @aikidosec/safe-chain) blocks malicious npm packages at install time.

Done when: the grep is clean, .env is untracked, public endpoints have a size/rate cap, and the demo uses no real personal data.

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.