agentleFS
conectlensconectlens/lenserfight/.agents/skills/security-reviewer/SKILL.md

security-reviewer

Skill18 starsChanged 6 months agoMITView on GitHub

Review LenserFight security for selected modules or scopes using architecture-aware, low-coupling, high-cohesion rules. Covers Supabase RLS, Edge Functions, React client, CLI auth, and Supabase auth flows.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ddd-architect, test-engineer and 9 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.
  • u9401066Skill

    ddd-architect

    Ensure code follows DDD architecture and DAL separation principles. Triggers: DDD, arch, 架構, 新功能, 新模組, new feature, scaffold, 骨架, domain.

    Also in 4 projects that use this

  • JohnJBorenSkill

    test-engineer

    Testing strategy, test patterns, and coverage optimization for unit, integration, and E2E tests

    Also in 3 projects that use this

  • u9401066Skill

    test-generator

    Generate comprehensive test suites including static analysis, unit tests, integration tests, E2E tests, and coverage reports. Triggers: TG, test, 測試, 寫測試, coverage, 覆蓋率, pytest, unittest, 驗證.

    Also in 3 projects that use this

  • victoralbinoSkill

    spec-writer

    Activity planning via deep interview. Use when the user asks to plan, specify, or detail any activity. Accepts an existing file or a direct description. Interviews with AskUserQuestion and writes the final spec.

    Also in 3 projects that use this

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 3 projects that use this

  • lodetomasiSkill

    tdd-workflow

    Test-Driven Development workflow with red-green-refactor pattern and best practices

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run a security review for $ARGUMENTS.

    line 8
  2. Distinctive:

    Prefer architectural reasoning over checklist dumping.

    line 15
  3. Very specific:

    Use libs/domain/* for domain behavior and libs/features/* for feature-level rules.

    line 17
  4. Distinctive:

    Prefer low coupling and high cohesion.

    line 40
  5. Distinctive:

    Avoid hidden security logic in decorators, interceptors, or mappers without explicit ownership.

    line 43
  6. Distinctive:

    Prefer explicit invariants, narrow interfaces, and single-responsibility security components.

    line 44

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

Run a security review for $ARGUMENTS.

Purpose Review security of the requested scope only. Scope may be modules, files, flows, guards, DTOs, migrations, logs, or cross-module interactions.

Approach

  • Let the requested scope drive the review depth.
  • Prefer architectural reasoning over checklist dumping.
  • Review only the code and docs needed for the given scope.
  • Use libs/domain/* for domain behavior and libs/features/* for feature-level rules.

Workflow [ ] 1 Resolve scope from $ARGUMENTS [ ] 2 Inspect relevant code, docs, and contracts [ ] 3 Identify trust boundaries, actors, assets, and entrypoints [ ] 4 Review authn, authz, validation, data exposure, abuse resistance, and failure handling [ ] 5 Check GRASP/OOAD quality where it affects security [ ] 6 Report findings by severity with exploit path and minimal remediation

Core review areas

  • authentication
  • authorization
  • tenant/workspace isolation
  • DTO and input validation
  • sensitive data exposure
  • idempotency and replay resistance
  • rate limiting and abuse controls
  • transactional integrity and race conditions
  • provider/webhook trust
  • logging and error sanitization

Design rules

  • Prefer low coupling and high cohesion.
  • Security-critical decisions should live in focused guards/services, not be scattered across controllers.
  • Controllers should coordinate; services enforce domain rules; guards/policies enforce access.
  • Avoid hidden security logic in decorators, interceptors, or mappers without explicit ownership.
  • Prefer explicit invariants, narrow interfaces, and single-responsibility security components.

Load references only when needed

Review process and severity model
See the reference guide

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.