agentleFS
Sign inStart free
cvszcvsz/zomega/skills/security-baseline/SKILL.md

security-baseline

Skill1 starsChanged 2 months agoMITView on GitHub

4 other projects use a version of this.

Adopted by

Most recently taken up by

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 3 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:

    Never reveal secret values, weaken authentication/TLS, bypass authorization, or perform destructive operations without explicit …

    line 19

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

zomega Skill 081: security-baseline

Owner

zomega-security

Objective

Execute security-baseline as a production engineering operation with traceable evidence.

Procedure

  1. Validate the supplied objective, scope, environment, and constraints.
  2. Inspect current-state evidence relevant to security-baseline before proposing change.
  3. Identify dependencies, trust boundaries, failure modes, and rollback requirements.
  4. Produce the smallest complete implementation or decision required by this capability.
  5. Validate the result with deterministic checks appropriate to the capability.
  6. Record changed artifacts, commands/results, risks, and unresolved external blockers.
  7. Return PASS only when required validation evidence is present; otherwise return FAIL or BLOCKED.

Security Contract

Never reveal secret values, weaken authentication/TLS, bypass authorization, or perform destructive operations without explicit authorization plus backup and rollback evidence.

Result Contract

Return structured fields: status, findings, changes, validation, evidence, blockers, next_action.

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