Skip to content
Back to skills

Axguard Report

ASecurity

Produce or polish AXguard Markdown and HTML audit reports from verified evidence. Use with /axguard-report. Prefer regenerating via axguard audit; tighten narrative only with confirmed findings.

  • 15 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
securitybashsql

Works with

  • cli

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add awarexone/AXguard --skill axguard-report --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Axguard Report?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Axguard Report
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/awarexone-axguard-report/badge)](https://www.skillsdirectory.com/skills/awarexone-axguard-report)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: axguard-report
description: Produce or polish AXguard Markdown and HTML audit reports from verified evidence. Use with /axguard-report. Prefer regenerating via axguard audit; tighten narrative only with confirmed findings.
---

# AXguard Report

Visual HTML is the human deliverable; Markdown for PRs/docs; JSON for CI. Prefer regenerating with the CLI; polish prose only with **verified** evidence. No filler. No exploit playbooks.

## Generate (preferred)

```bash
axguard audit . --out-dir .findings/axguard
```

Artifacts:

```
.findings/axguard/axguard-report.html
.findings/axguard/axguard-report.md
.findings/axguard/axguard-report.json
```

If a report already exists, refine MD from triage Keep list; do not invent findings the scanner and review did not support.

## Narrative structure (Markdown polish)

1. **Executive summary** — decision hint (blockers Y/N), C/H/M/L counts, scope (path, date).
2. **Method** — `axguard audit` / `axguard scan` + human triage. One short paragraph.
3. **Findings** — confirmed only, severity-sorted. Each item:

```
### [SEVERITY] Title
- CWE / OWASP: …
- Location: path:line
- Impact: one sentence
- Evidence: source → sink (no live exploit steps)
- Fix: one or two sentences
- Status: open | fixed | accepted risk
```

4. **Dropped / noise** — optional short appendix (count + themes), not a second findings list.
5. **Next steps** — fix order, re-audit, CI gate (`/axguard-ci`).

## Evidence rules

- Every finding cites file:line or config key.
- Impact language matches confidence (`axguard-cso` gate).
- Map classes using `axguard-knowledge` names (IDOR, SQLi, SSRF, …) for consistency.
- Screenshots/HTML: keep scanner HTML as visual source of truth; do not strip severity colors when hand-editing.

## Tone

Shuvonsec / AwareXone: professional, terse, ship-oriented. State blast radius; skip drama and padding.

## Output contract

Tell the user exact paths and tally:

```
Critical: N
High: N
Medium: N
Low: N
Reports: .findings/axguard/axguard-report.{md,html,json}
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.