agentleFS
Sign inStart free
precise-alloyprecise-alloy/ritus/skills/security/SKILL.md

security

Skill1 starsChanged 4 months agoMITView on GitHub

Loaded automatically by execute-task and verify-task when changes touch auth, billing, migration, tenant isolation, infra, or shared contracts - security checklist. Do not invoke standalone unless the user specifically asks for a security review

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 100 edited versions we read keep these.

  • 10

    Distinctive

    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:

    All checklist items are hard gates - must pass before reporting done.

    line 13
  2. Very specific:

    Every DB query touching user data must filter by the ownership key (e.g.

    line 17
  3. Distinctive:

    Never trust client-supplied entity IDs without verifying ownership against the session.

    line 24
  4. Distinctive:

    No secrets in: source code, git history, logs, error messages, or API responses.

    line 36
  5. Distinctive:

    All secrets live in environment variables only - never in code or DB plaintext.

    line 37
  6. Distinctive:

    No string interpolation in DB queries - parameterized queries or ORM always.

    line 42
  7. Distinctive:

    No user input passed to shell commands.

    line 43
  8. Distinctive:

    All user-generated content rendered in frontend must be HTML-escaped.

    line 48
  9. Very specific:

    No raw innerHTML with untrusted content.

    line 49
  10. Distinctive:

    No arbitrary URL fetch from user-supplied input without validation.

    line 54
  11. Distinctive:

    Write to an audit log for: state-changing actions, permission changes, destructive operations.

    line 58
  12. Distinctive:

    Never silently overwrite important records - version or snapshot before overwriting.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 100 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 Standards

When to use

Load this skill for any task touching auth, billing, migrations, tenant isolation, infra config, or shared contracts. All checklist items are hard gates - must pass before reporting done.

Tenant / user data isolation

  • Every DB query touching user data must filter by the ownership key (e.g. tenantId, orgId, userId).
  • The ownership key must come from the authenticated session - never from the request body.
  • Data retrieval must scope to the authenticated entity - no cross-tenant data access.

Input validation

  • Validate at system boundaries: API endpoints, job/queue inputs, webhook handlers.
  • Never trust client-supplied entity IDs without verifying ownership against the session.
  • Validate enum values explicitly before use in DB queries or business logic.
  • File uploads: validate MIME type + extension + max size before processing.

Authentication and authorization

  • Token/session verification in middleware - not inside route handlers.
  • Role checks are explicit per endpoint - "authenticated" does not imply "authorized."
  • Integration tokens and API credentials must be encrypted at rest before storage.

Secret handling

  • No secrets in: source code, git history, logs, error messages, or API responses.
  • All secrets live in environment variables only - never in code or DB plaintext.
  • Application validates required env vars at startup - fail fast if missing.

Injection prevention

  • No string interpolation in DB queries - parameterized queries or ORM always.
  • No user input passed to shell commands.
  • User-supplied content stored in DB must be sanitized if it will be rendered as HTML.

Output encoding

  • All user-generated content rendered in frontend must be HTML-escaped.
  • No raw innerHTML with untrusted content.

SSRF (Server-Side Request Forgery) prevention

  • External URL fetching must validate against a configured allowlist.
  • No arbitrary URL fetch from user-supplied input without validation.

Audit logging

  • Write to an audit log for: state-changing actions, permission changes, destructive operations.
  • Required fields: actorId, entityType, entityId, action, beforeSnapshot, afterSnapshot.
  • Never silently overwrite important records - version or snapshot before overwriting.

Checklist (required for all safety override changes)

  • Tenant/ownership scoping verified on all new queries
  • No new secrets in code or logs
  • Auth/authz enforced in middleware, not handler
  • Sensitive fields encrypted before persistence
  • Audit log entry created for state changes
  • Input validation present at system boundary
  • No raw SQL string interpolation
  • Classified STANDARD or above - no TRIVIAL/SIMPLE for safety override changes

Handoff

  • Report: the standard applied to the parent skill's work.

Download now (ZIP)

  • Other versions122 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 122

    1. BuilderIO/agent-native★ 7.4ksame name
    2. parcadei/Continuous-Claude★ 3.9ksame name
    3. parcadei/Continuous-Claude-v2★ 3.9ksame name
    4. parcadei/Continuous-Claude-v3★ 3.9ksame name
    5. gridaco/grida★ 2.7ksame name
    6. static-web-server/static-web-server★ 2.4ksame name
    7. BankrBot/skills★ 1.2ksame name
    8. BankrBot/openclaw-skills★ 1.2ksame name
    9. alinaqi/maggy★ 711same name
    10. alinaqi/claude-bootstrap★ 708same name

    112 more not listed

    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.

  • Used alongsideProjects with it also use cost-reducer, albert-dm and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • huyvpSkill

      cost-reducer

      Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.

      Also in 12 projects that use this

    • vikneshwaran16032005-altSkill

      albert-dm

      Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).

      Also in 6 projects that use this

    • vikneshwaran16032005-altSkill

      new-client-system

      Scaffold a new client's full stack — Next.js 16 frontend dashboard + Trigger.dev backend worker — from the Shiney automations template. Use when the user says "new client", "onboard a client", "scaffold a client system", "set up <client-name>", or wants to start a fresh frontend+backend project styled and structured like the Shiney automations dashboard. Produces structure only; no automations are scaffolded — those are added later.

      Also in 6 projects that use this

    • ffsshhttiikkSkill

      scalability

      Core foundational concepts and principles for Scalability

      Also in 11 projects that use this

    • xfstudioSkill

      trigger-dev

      Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

      Also in 11 projects that use this

    • xfstudioSkill

      customer-support

      Elite AI-powered customer support specialist mastering

      Also in 12 projects that use this

    • +4 more from vikneshwaran16032005-alt
  • In this repository21 other files it gives its agents.

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