agentleFS
Sign inStart free
MesteriisMesteriis/Engineering-Bible-AI/skills/security-diff-review/SKILL.md

security-diff-review

Skill0 starsChanged 4 months agoMITView on GitHub

Routes an authorized Git diff security review to the original native security-diff-scan skill.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    If the original provider or a required capability is missing, the route is unavailable.

    line 13
  2. Distinctive:

    Keep exploitability, confirmed findings and unknowns tied to source evidence.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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 Diff Review

Load and follow the complete original codex-security:security-diff-scan skill exposed by the current host. Its references, capability preflight, findings and completion contracts remain native author responsibilities. This adapter selects the provider and does not reproduce its scan stages.

If the original provider or a required capability is missing, the route is unavailable. Use the host's official Codex Security plugin setup to install or enable it and refresh session exposure. Do not use abbreviated local scan steps as a counterfeit fallback or claim completion from registration.

Owner Policy

  • Review authorized code and the user's selected Git range or working-tree patch. Preserve unrelated changes and private machine state.
  • Review-only by default; do not patch findings without an explicit fix request. Route authorized remediation to fix-security-finding.
  • Keep exploitability, confirmed findings and unknowns tied to source evidence.
  • Return the original provider's report and actual coverage, validation results and unresolved gaps. A failed or skipped gate is not PASS.

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.

Check your setup, free