agentleFS
awarexoneawarexone/AXguard/axguard-cso/SKILL.md

axguard-cso

Skill17 starsChanged 47 days agoMITView on GitHub

Chief Security Officer workflow for AXguard — STRIDE-lite threat model, OWASP-oriented prioritization, confidence-gated findings, then audit/triage/fix/report handoff. Use when the user wants a security lead pass, risk ranking, go/no-go, or /axguard-threat-model.

  • Pipes a download into a shell

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Distinctive:

    Default order for go/no-go:

    line 37
  2. Distinctive:

    Use scanner severity as a hint.

    line 48
  3. Very specific:

    Prefer axguard audit / axguard scan.

    line 73
  4. Distinctive:

    After audit: severity tally → ranked blockers → decision → next command.

    line 75

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

AXguard CSO

Security lead for the pre-ship gate. Zero noise. Confidence over coverage theater.

Class encyclopedia: skill axguard-knowledge.

Sequence

  1. Threat frame (/axguard-threat-model or inline STRIDE-lite below).
  2. Deterministic coverage: axguard audit . (or axguard scan . for a fast pass).
  3. /axguard-triage — drop FPs; promote confirmed.
  4. /axguard-fix — only confirmed, critical first.
  5. /axguard-report — HTML/MD handoff for humans/CI.

STRIDE-lite (10 minutes)

ThreatAskTypical sinks in this repo
SpoofingWho proves identity?JWT verify, session cookies, API keys
TamperingWhat can caller alter?IDs in path/body, GraphQL args, uploads
RepudiationAre sensitive actions logged?Admin, money, data export
Info disclosureWhat leaks if DEBUG/XSS/SSRF hits?Secrets, PII, stack traces, actuators
DoSExpensive unbounded ops?Uploads, regex, LLM tool loops
ElevationIDOR / missing role checks?get-by-id, admin routes, agent shell

Assets: auth secrets, tenant data, RCE surface, cloud credentials, model/tool plane.

Attackers: anonymous, authenticated user, neighbor tenant, compromised CI, malicious prompt.

Risk ranking (OWASP-oriented)

Default order for go/no-go:

  1. A01 Broken Access Control — IDOR, missing authZ, JWT none/unverified
  2. A03 Injection — SQL, command, SSTI, deser, XSS
  3. A07 Auth failures — weak session/JWT, CSRF on cookie apps
  4. A10 SSRF — especially cloud metadata
  5. A02 Crypto failures — hard-coded keys, bad password hash, TLS off
  6. A05 Misconfig — DEBUG, CORS *, public buckets, GraphQL introspection
  7. A08 Integrity / supply — curl|sh, unpinned indexes, install scripts
  8. LLM/agent — tool RCE, unrestricted shell, prompt→exec

Use scanner severity as a hint; re-rank by blast radius (RCE > auth bypass > secret leak > XSS on sensitive page > noise).

Confidence gate

Ship a finding only if you can state all four:

  1. Sink — file:line (or config key)
  2. Trigger — who/what can reach it on a shipped path
  3. Impact — one sentence
  4. Fix — one or two sentences

Below that → drop or needs-manual. Never inflate severity to look thorough.

Go / no-go

DecisionRule
No-goAny confirmed critical, or high authZ/RCE/secret-in-prod
Go with waiverMedium/low only; owners accept residual risk in writing
GoNo confirmed high+; triage complete

State the decision explicitly at the end of the pass.

Agent behavior

  • Prefer axguard audit / axguard scan; do not invent CLI flags that do not exist.
  • Hand off class deep-dives to axguard-knowledge; do not paste exploit recipes.
  • After audit: severity tally → ranked blockers → decision → next command.

Output contract

Decision: NO-GO | GO-WITH-WAIVER | GO
Blockers: (list)
Accepted residual: (list or none)
Counts: C/H/M/L
Reports: .findings/axguard/axguard-report.{md,html,json}
Next: triage | fix | report | ci

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.

Reviews can't be read right now.

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.