agentleFS
emanuelegreco29emanuelegreco29/codexpiator/skills/codexpiator-security/SKILL.md

security

Skill1 starsChanged 6 days agoMITView on GitHub

Security guidance - secure coding checklist, authn/authz threat-model and hardening (MFA, IDOR/BOLA, session fixation, password-reset abuse - see codexpiator:backend for base auth implementation), input validation and injection defense, secrets and config management, dependency and supply-chain risk, infrastructure and access control, business-logic/webhook security, AI/agent security (prompt injection, excessive AI permissions), and security testing. Use for any security-sensitive question or before shipping anything that touches auth, user input, payments, AI/agent features, or infrastructure config.

  • Reads credentials

139 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use albert-dm, cost-reducer 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.
  • yawningwhaleAISkill

    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 5 projects that use this

  • 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 11 projects that use this

  • yawningwhaleAISkill

    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 5 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 10 projects that use this

  • ffsshhttiikkSkill

    scalability

    Core foundational concepts and principles for Scalability

    Also in 11 projects that use this

  • h-mascotSkill

    self-healing

    Wrap long-running or fragile OpenClaw work in checkpointed retries, watchdogs, fallback models, and proof-of-completion so failed subagents can resume instead of silently dying.

    Also in 11 projects that use this

  • +3 more from yawningwhaleAI

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 115 edited versions we read keep these.

  • 1

    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:

    Read the relevant checklist(s) for the surface being touched and verify each applicable item against the actual code — don't treat this …

    line 37

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

Codexpiator Security

Single-purpose reference files for security concerns. This skill is a fast, always-available baseline — it is not a substitute for a real specialized security audit when one is available.

FileRead this when...
secure-coding-checklist.mdQuick OWASP-Top-10-mapped pass over any change
authn-authz-patterns.mdLogin, sessions, MFA, password reset, IDOR/BOLA, privilege checks
input-validation-and-injection.mdAnything touching user input: SQL/NoSQL injection, XSS, CSRF, uploads, path traversal, SSRF, mass assignment, command injection, deserialization
secrets-and-config-management.mdCredentials, .env files, secrets in git/JS/logs, cookies, browser storage
dependency-and-supply-chain.mdVulnerable/malicious packages, CI/CD supply-chain risk
infrastructure-and-access-control.mdCloud/DB permissions, admin routes, debug tools, headers, CORS, rate limits, monitoring, backups
business-logic-and-webhooks.mdPayments, webhooks, business-logic abuse, race conditions
security-testing.mdHow to actually test security controls, not just implement them

Mandatory: use Anthropic's claude-security plugin, install it if missing

For any security-sensitive work (auth, payments, user input handling, infrastructure config, anything pre-merge on a security-critical path), follow ${CLAUDE_PLUGIN_ROOT}/shared/claude-security-plugin.md: check for claude-security:claude-security, install it without asking if absent, and invoke it before finalizing the change. Then also run security-review when available. This skill's own checklists are the fast baseline that runs next to them, and the fallback only when the plugin genuinely can't be installed — not a substitute you reach for by default instead of checking.

Every principle here needs to actually be applied, not just known

Read the relevant checklist(s) for the surface being touched and verify each applicable item against the actual code — don't treat this skill's content as background knowledge that informs a general sense of caution. A checklist item that isn't checked against the real diff provides no protection.

Ask when useful; suggest an audit after significant work

See ${CLAUDE_PLUGIN_ROOT}/shared/collaboration-and-audit-practice.md — ask a targeted clarifying question (via AskUserQuestion when available) when a security trade-off genuinely needs the user's input, and suggest /codexpiator:audit after significant security-sensitive work.

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.