⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v0.5.0

absolute-audit

maddhruv@maddhruv⭐ 223 stars· last commit 20d ago· 0 open issues

>

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

β€”/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐ 223 on GitHubGitHub β†—

Popular

🟒ProSkills Score
β€”
πŸ“

Not yet listed on ClawHub or SkillsMP

// README

absolute-audit

Vulnerability and security scan for your own repo. Finds dependency CVEs plus risky code patterns (secrets, injection, weak authz), triages by severity Γ— reachability, and remediates without suppressing.

Quick Facts

FieldValue
Categoryworkflow
Version0.5.0
Platformsclaude-code, gemini-cli, openai-codex, mcp
LicenseMIT

How to Install

npx skills add maddhruv/absolute-audit

Usage

/absolute-audit "Scan the repo for vulnerable deps and security issues"
/absolute-audit "Are we vulnerable to any CVEs?"

Authorized defensive use β€” audits your own repository. Complements the built-in /security-review (which reviews the pending diff).

Maintainers

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/absolute-audit/SKILL.md4.6 KBupstream β†—
    ---
    name: absolute-audit
    version: 0.5.0
    description: >
      Vulnerability and security scan (defensive, your own repo): dependency CVEs plus risky code patterns (secrets, injection, weak authz), severity x reachability triaged and remediated without suppressing. Complements the built-in /security-review.
      Triggers on "absolute audit", "security audit", "are we vulnerable", "scan for CVEs", "check for secrets/injection", "harden this".
    category: workflow
    tags:
      - workflow
      - security
      - audit
      - vulnerabilities
      - cve
    platforms:
      - claude-code
      - gemini-cli
      - openai-codex
      - mcp
    user-invocable: true
    argument-hint: "[target]"
    license: MIT
    maintainers:
      - github: maddhruv
    ---
    
    > Start your first response with the πŸ”’ emoji.
    
    ## Absolute Audit
    
    Find and triage security problems across the repo β€” vulnerable dependencies (CVEs) and
    risky code patterns β€” then fix the ones worth fixing, safely. Output is a severity-ranked
    findings table with a remediation per item, not a raw scanner dump.
    
    Runs the shared engine in **`references/health-engine.md`** β€” read it for the
    DETECT β†’ SCAN β†’ TRIAGE β†’ FIX β†’ VERIFY β†’ REPORT loop and the safety contract. This file
    covers only what's specific to security auditing.
    
    > **Authorized defensive use.** This command audits the user's *own* repository to find
    > and fix weaknesses. It is for hardening, not for attacking systems or evading detection.
    
    ---
    
    ## When to use
    
    - "Run a security audit", "are we vulnerable?", "check our deps for CVEs".
    - After a CVE disclosure affecting something you use.
    - Periodic hygiene on `main`.
    
    Distinct from the built-in **`/security-review`** (reviews the *pending diff* on your
    branch) β€” `audit` scans the **whole committed repo**, deps included. They complement.
    
    ---
    
    ## What it scans
    
    **1. Dependency vulnerabilities (CVEs)** β€” primary:
    
    | Ecosystem | Scanner |
    |---|---|
    | npm / pnpm / yarn | `npm audit --json` / `pnpm audit --json` / `yarn npm audit --json` |
    | Python | `pip-audit` (preferred) or `safety check` |
    | Go | `govulncheck ./...` |
    | Cross-language | `osv-scanner` against the lockfile if available |
    
    **2. Code-level patterns** β€” read-only grep/static pass for high-signal issues only:
    hardcoded secrets/keys/tokens, `eval`/dynamic exec on input, SQL built by string
    concatenation, missing authz checks on sensitive routes, disabled TLS verification, unsafe
    deserialization, overly-broad CORS. Prefer the project's existing SAST/linter security
    rules (`eslint-plugin-security`, `bandit`, `gosec`) if configured.
    
    Report suspected leaked secrets but **never print the secret value** β€” reference
    `path:line` and the kind.
    
    ---
    
    ## Risk ranking (TRIAGE)
    
    Rank by **severity Γ— exploitability Γ— reachability**, not raw CVSS:
    
    | Severity | Default |
    |---|---|
    | Critical / High, reachable, fix available | fix now (wave 1) |
    | Moderate, reachable | fix this pass |
    | Low / not reachable from app code | report, usually defer |
    | Transitive-only, no direct upgrade path | flag, note the blocking parent |
    
    Mark each: is it reachable from the app's actual code paths? A CVE in an unused transitive
    branch is lower priority than a Moderate one on a hot path. State the fixed version or the
    mitigation for each.
    
    ---
    
    ## Fix & verify
    
    - **Dep CVEs** β†’ resolve via the smallest version move that clears it (delegate the actual
      bump mechanics to the `upgrade` flow's per-ecosystem steps). Prefer patched minors;
      escalate to a major only when that's the only fix, and gate it.
    - **Code issues** β†’ apply the concrete fix (parameterize the query, move the secret to env
      + flag the leaked one for rotation, add the authz check). Each fix is its own small wave.
    - After each wave, re-run the scanner: the finding must actually disappear, and tests/build
      stay green. Never resolve by suppressing/allowlisting the alert.
    - Leaked live secrets: flag for **rotation** β€” removing from code doesn't undo exposure.
    
    ---
    
    ## Gotchas
    
    1. **Audit fatigue β†’ blanket ignore.** Triage by reachability instead of muting the scanner.
    2. **Fixing a CVE by suppressing it.** An allowlisted advisory is still a vulnerability.
    3. **Printing the secret.** Reference location + type only; never echo the value.
    4. **Deleting a secret from code β‰  safe.** It's in git history and was exposed β€” rotate it.
    5. **Stopping at deps.** Many real issues are in code, not the dependency tree β€” run both passes.
    
    ---
    
    ## Companion commands
    
    - **`/absolute upgrade`** β€” does the actual version moves for vulnerable deps.
    - **`/security-review`** (built-in) β€” pair with this to also cover your pending diff.
    - **`/absolute work`** β€” if remediation is a real refactor (e.g. replacing an auth flow), hand off.
    
  • README.mdupstream β†—

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/maddhruv-absolute-skills-absolute-audit.md

// REPO STATS

223 stars
0 open issues
Last commit: 20d ago