Cyber Framework Mapping

What it does

When your agent uses it

• Mapping exercise observations
• Procedures to NIST
• Another named framework

Example prompts

• “Use the cyber-framework-mapping skill to maintain sparse, reviewable cybersecurity framework edges with versioned IDs, relation, rationale, source…”
• “/cyber-framework-mapping”

Workflow steps

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

1. 1Name framework, version, stable ID, and exact source URL or document section.
2. 2Choose relation (supports, describes, observed-as, partial, unknown, or conflicts).
3. 3Write a bounded rationale tied to an evidence record, not a generic similarity.
4. 4Set review status: reviewed, needs-review, or unreviewed; include reviewer and date when reviewed.
5. 5Preserve empty or unknown mappings explicitly; do not infer a complete catalog.
6. 6On a version/source change, preserve the prior versioned edge and its evidence unchanged. Create a separately versioned candidate linked…

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 Framework Mapping loads about 584 tokens when it runs, and up to ~785 if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 213 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~62

When it runs · the whole SKILL.md, loaded when a task matches

~584

With references · SKILL.md plus every file in references/, read only if the agent opens them

~785

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

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). 213 words, ~584 tokens.

name

cyber-framework-mapping

description

Maintains sparse, reviewable cybersecurity framework edges with versioned IDs, relation, rationale, source, and review status. Use when mapping exercise observations or procedures to NIST, ATT&CK, or another named framework.

guardrail

true

metadata.labels

cybersecurity, framework-mapping, provenance

cyber-framework-mapping/
├── SKILL.md
├── references/edge-record.md
└── evals/evals.json

© 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-framework-mapping of HoangNguyen0403/agent-skills-standard.

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

Open the folder on GitHubat commit b529c2d