agentleFS
Sign inStart free
kenhuanguskenhuangus/defense-factory-skills/skills/security-scan/SKILL.md

security-scan

Skill2 starsChanged 47 days agoMITView on GitHub

Runs authorized defensive discovery across inventoried assets and writes finding candidates for the Defense Factory Discovery phase. Use for baseline or periodic scans, not for unauthorized offensive testing.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 74 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer security-diff-scan instead when only a PR/diff is in scope

    line 15
  2. Distinctive:

    Read inventory and threat priorities.

    line 25
  3. Distinctive:

    Run defensive checks only, for example:

    line 26
  4. Very specific:

    Add a run log .defense-factory/findings/candidates/_scan-run-<timestamp>.md listing tools, versions, commands, and asset ids.

    line 33
  5. Very specific:

    Do not set status to validated from this skill.

    line 50
  6. Distinctive:

    Do not produce weaponized exploit payloads.

    line 51

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

Phase: Discovery
Style: Blue (defensive)

When to use

  • Inventory exists under .defense-factory/inventory/
  • Full or periodic discovery is requested
  • Prefer security-diff-scan instead when only a PR/diff is in scope

Preconditions

  1. Written authorization / ownership for targets in SECURITY.md.
  2. Inventory entries with ids for assets to scan.
  3. Tooling available in the environment (language scanners, dependency audit, secret scanners, config linters). Use what the repo already supports; do not install malware or attack frameworks.

Procedure

  1. Read inventory and threat priorities; select in-scope assets.
  2. Run defensive checks only, for example:
    • Dependency vulnerability audit (npm audit, pip-audit, etc. as applicable)
    • Secret scanning on repo contents
    • SAST / linters the project already uses
    • Misconfiguration checks on IaC the user owns
  3. For each issue, write a candidate finding (status: "candidate") per schemas/finding.schema.json without claiming validation.
  4. Save each file to .defense-factory/findings/candidates/<id>.json.
  5. Add a run log .defense-factory/findings/candidates/_scan-run-<timestamp>.md listing tools, versions, commands, and asset ids.
  6. Validate candidates:
python <skills-repo>\scripts\validate_artifacts.py .defense-factory\findings\candidates\<id>.json --schema finding

Required outputs

PathNotes
.defense-factory/findings/candidates/*.jsonstatus=candidate
.defense-factory/findings/candidates/_scan-run-*.mdTooling log

Stop / refuse

  • Refuse unauthorized offensive scanning of third-party systems.
  • Do not set status to validated from this skill.
  • Do not produce weaponized exploit payloads; record location and descriptive risk only.

Next phase

triage-validate-finding for dynamic confirmation; optionally dedupe-findings if volume is high.

Download now (ZIP)

  • Other versions83 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 83

    1. openai/codex-security★ 11ksame name
    2. openai/plugins★ 7.4ksame name
    3. zereight/gitlab-mcp★ 2.1ksame name
    4. heartleo/zlib★ 1.2ksame name
    5. bagofwords1/bagofwords★ 463same name
    6. loulanyue/awesome-claude-notes★ 272same name
    7. Resgrid/Core★ 235same name
    8. GoogleCloudPlatform/cloud-solutions★ 138same name
    9. Fmarzochi/EGC★ 61same name
    10. drvoss/everything-copilot-cli★ 49same name

    73 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 django-security, springboot-security 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.
    • mstuder-slalomSkill

      django-security

      Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

      Also in 5 projects that use this

    • mstuder-slalomSkill

      springboot-security

      Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

      Also in 4 projects that use this

    • royaluniondesign-sysSkill

      deployment-patterns

      Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

      Also in 5 projects that use this

    • romaintoso78Skill

      security-bounty-hunter

      Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.

      Also in 3 projects that use this

    • DonTiziSkill

      dependency-check

      Analyze project dependencies for outdated packages, security vulnerabilities, and licensing issues. Use for dependency audits and maintenance.

      Also in 3 projects that use this

    • nek1987Skill

      postgres-patterns

      PostgreSQL patterns for reviewing migrations and writing efficient queries. Use when reviewing Alembic migrations, optimizing queries, or debugging database issues.

      Also in 6 projects that use this

    • +2 more from mstuder-slalom
  • In this repository10 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.

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.

Check your setup, free