Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations.

MITAuto-check passedSecurity

Install Cyber Evidence

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill cyber-evidence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard cyber-evidence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cybersecurity/cyber-evidence .claude/skills/cyber-evidence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cyber-evidence
GitHub stars
572
Token cost
~630 tokens
SKILL.md length
207 words
Files
3 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations.

  • Works in 6 steps: Bind record to engagement_scope_ref,… → Capture observed_at, observer, method,… → Set exactly one finding_status:… → …
  • Recording exercise evidence
  • SKILL.md covers Priority: P0 (CRITICAL), Structure, Workflow and Rules, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cyber Evidence is an agent skill from HoangNguyen0403/agent-skills-standard. Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations. Use when recording exercise evidence, findings, validation results, or security-review handoffs.

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/evidence-record.md`).

It sits in Security, covering Security review. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • Recording exercise evidence
  • Validation results
  • Security-review handoffs

Example prompts

  • “Use the cyber-evidence skill to capture redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth…”
  • “/cyber-evidence”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Bind record to engagement_scope_ref, skill_version, and source.
  2. Capture observed_at, observer, method, and evidence references; redact secrets and sensitive payloads.
  3. Set exactly one finding_status: confirmed, suspected, blocked, not-tested, or false-positive.
  4. State limitations, missing runtime controls, synthetic-data boundaries, and accountable owner.
  5. Preserve independently held ground truth; compare it only through an independent adjudicator.
  6. Update the canonical artifacts/security-review.md when a workflow chain already owns that artifact.

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cyber Evidence loads about 630 tokens when it runs, and up to ~864 if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 207 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~630
With references · SKILL.md plus every file in references/, read only if the agent opens them
~864

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 207 words, ~630 tokens.

Download SKILL.mdSave it as .claude/skills/cyber-evidence/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
cyber-evidence
description
Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations. Use when recording exercise evidence, findings, validation results, or security-review handoffs.
guardrail
true
metadata.labels
cybersecurity, evidence, provenance

Cyber Evidence

Priority: P0 (CRITICAL)

Record what was observed, how it was sourced, and what remains unknown; never turn absence of proof into proof.

Structure

text
cyber-evidence/
├── SKILL.md
├── references/evidence-record.md
└── evals/evals.json

Workflow

  1. Bind record to engagement_scope_ref, skill_version, and source.
  2. Capture observed_at, observer, method, and evidence references; redact secrets and sensitive payloads.
  3. Set exactly one finding_status: confirmed, suspected, blocked, not-tested, or false-positive.
  4. State limitations, missing runtime controls, synthetic-data boundaries, and accountable owner.
  5. Preserve independently held ground truth; compare it only through an independent adjudicator.
  6. Update the canonical artifacts/security-review.md when a workflow chain already owns that artifact. Shared record fields: engagement_scope_ref, skill_version, source, observed_at, finding_status, evidence_refs, limitations, accountable_owner.

Rules

  • Hashes and timestamps support provenance; they do not prove trusted origin or efficacy.
  • Keep raw evidence separate from sanitized reports; never persist credentials, real secrets, or unnecessary personal data.
  • Preserve blocked and not-tested outcomes; do not downgrade them into clean results.
  • Promotion requires independent review; an operator cannot approve their own result.
  • Link authorization and mapping only when evidenced.

Anti-Patterns

  • No scanner-only finding: Corroborate tool output or mark suspected.
  • No invented certainty: Use limitations and status fields.
  • No unredacted persistence: Minimize and sanitize before storage.
  • No rewritten history: Append corrections with provenance.

References

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/cybersecurity/cyber-evidence of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/evidence-record.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Cyber Evidence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cyber Evidence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cyber Evidence this skillHoangNguyen0403/agent-skills-standard572—~630Automated safety check: PassMIT
Deepsec Documentation Guidevercel-labs/deepsec8.1k—~956Automated safety check: PassApache-2.0
Kubernetes Network Security Auditkubeshark/kubeshark12k—~7.3kAutomated safety check: NotesApache-2.0
Native Dependency Updatemono/SkiaSharp5.6k—~4.1kAutomated safety check: PassMIT
Semgrep Security Scantrailofbits/skills7.5k—~3.7kAutomated safety check: NotesCC-BY-SA-4.0
Skillward AuditFangcun-AI/SkillWard143—~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Deepsec Documentation Guide

    vercel-labs/deepsec

    Official

    Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.

    8.1k GitHub stars~956 tokensUpdated 12 days ago
    SecurityAuto-check passed
  • Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.

    12k GitHub stars~7.3k tokensUpdated yesterday
    SecurityAuto-check: notes
  • Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.

    5.6k GitHub stars~4.1k tokensUpdated yesterday
    SecurityAuto-check passed
  • Semgrep Security Scan

    trailofbits/skills

    Official

    Detects languages, proposes rulesets for approval, then runs the approved Semgrep scan across a codebase and merges the output into one SARIF file.

    7.5k GitHub stars~3.7k tokensUpdated yesterday
    SecurityAuto-check: notes
  • Skillward Audit

    Fangcun-AI/SkillWard

    Security-audit a third-party skill bundle (folder with SKILL.md, or .zip / .tar.gz archive) before installing it, using the SkillWard cloud scanner.

    143 GitHub stars~2.9k tokensUpdated 2 mo ago
    SecurityAuto-check passed
  • Security Audit

    TheDecipherist/claude-code-mastery

    Checks a codebase for hardcoded secrets, vulnerable dependencies, weak input handling, weak authentication and unsafe transport settings before deployment or merge.

    551 GitHub stars~1.3k tokensUpdated 5 mo ago
    SecurityAuto-check: notes

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo
  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated yesterday
    Auto-check passed
  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated yesterday
    Auto-check passed
  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated yesterday
    Auto-check passed
  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Cyber Evidence

What does Cyber Evidence do?

Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations. Cyber Evidence is an agent skill from HoangNguyen0403/agent-skills-standard. Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations.

When should I use Cyber Evidence?

Cyber Evidence fits situations like: recording exercise evidence; validation results; security-review handoffs.

How do I install Cyber Evidence in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill cyber-evidence -a claude-code`. Or copy the skill folder (skills/cybersecurity/cyber-evidence in HoangNguyen0403/agent-skills-standard) into .claude/skills/cyber-evidence in your project. Claude Code loads it when a task matches its description.

How do I install Cyber Evidence in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill cyber-evidence -a codex`. Or copy the skill folder (skills/cybersecurity/cyber-evidence in HoangNguyen0403/agent-skills-standard) into .agents/skills/cyber-evidence in your project. Codex loads it when a task matches its description.

Can I use Cyber Evidence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill cyber-evidence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cyber-evidence, .gemini/skills/cyber-evidence, .github/skills/cyber-evidence and .opencode/skills/cyber-evidence in your project.

What does Cyber Evidence need to run?

SKILL.md names no scripts, command-line tools or credentials: Cyber Evidence is instructions for the agent only.

Does Cyber Evidence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cyber Evidence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cyber Evidence use?

Cyber Evidence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cyber Evidence use?

About 630 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 234 tokens, read only when the agent opens those files.

What are the alternatives to Cyber Evidence?

Skills that share tags, products or a category with Cyber Evidence: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Kubernetes Network Security Audit (kubeshark/kubeshark, 12k stars), Native Dependency Update (mono/SkiaSharp, 5.6k stars) and Semgrep Security Scan (trailofbits/skills, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cyber Evidence?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.