agentleFS
Sign inStart free
MesteriisMesteriis/Engineering-Bible-AI/skills/fix-security-finding/SKILL.md

fix-security-finding

Skill0 starsChanged 4 months agoMITView on GitHub

Routes an explicitly requested security fix to the original native fix-finding skill with owner authorization and scope rules.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Very specific:

    Use only when the user explicitly asks to fix and verify a security vulnerability.

    line 8
  2. Distinctive:

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

    line 14

≈ “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

Fix Security Finding

Use only when the user explicitly asks to fix and verify a security vulnerability. Load and follow the complete original codex-security:fix-finding skill exposed by the current host, including its references and remediation-stage constraints. Preserve native ownership; this adapter does not reproduce the patch or verification workflow.

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 silently substitute a condensed local fix procedure or report a pending provider as completed.

Owner Policy

  • The user's finding, target and authorized remediation stage bound the work. Preserve unrelated findings, local changes and legitimate behavior.
  • Review authorization does not authorize fixes, and preparation does not authorize deployment or publication. Reuse authorization already granted.
  • Protect credentials, private runtime configuration and raw sensitive data.
  • Report the original provider's actual outcome, changed files, exact validation results and remaining proof gaps without weakening its evidence.

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