New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cyber Engagement Planning

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates.

MITAuto-check passedBackend & APIs

Install Cyber Engagement Planning

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

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

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard cyber-engagement-planning --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-engagement-planning .claude/skills/cyber-engagement-planning && 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-engagement-planning
GitHub stars
572
Token cost
~681 tokens
SKILL.md length
221 words
Files
3 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates.

  • Works in 7 steps: State objective, success observation,… → List in-scope synthetic assets or… → Assign requester, approver, operator,… → …
  • Preparing an exercise
  • 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 Engagement Planning is an agent skill from HoangNguyen0403/agent-skills-standard. Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.

Its SKILL.md is about 680 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/engagement-brief.md`).

It sits in Backend & APIs, covering Authorization and RBAC. 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

  • Preparing an exercise
  • Assessment plan before execution

Example prompts

  • “Use the cyber-engagement-planning skill to draft bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization…”
  • “/cyber-engagement-planning”

Workflow steps

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

  1. State objective, success observation, engagement/scope reference, dates, and accountable owner.
  2. List in-scope synthetic assets or explicitly authorized targets; list exclusions and non-goals.
  3. Assign requester, approver, operator, exercise control, adjudicator, and escalation roles.
  4. Record allowed actions, prohibited actions, data handling, communications, and runtime controls.
  5. Define expiry, stop triggers, restart authority, evidence fields, and unresolved decisions.
  6. Mark live execution blocked and the plan offline-only when required runtime support is absent; never imply production readiness.
  7. Restart requires both current authorization and verified host enforcement of scope. Owner approval, risk acceptance, documented…

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 Engagement Planning loads about 681 tokens when it runs, and up to ~899 if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 221 words of instructions outside code blocks.

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

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). 221 words, ~681 tokens.

Download SKILL.mdSave it as .claude/skills/cyber-engagement-planning/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
cyber-engagement-planning
description
Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.
guardrail
true
metadata.labels
cybersecurity, engagement-planning, scope

Cyber Engagement Planning

Priority: P0 (CRITICAL)

Produce a reviewable plan that separates intended activity from host-enforced permission.

Structure

text
cyber-engagement-planning/
├── SKILL.md
├── references/engagement-brief.md
└── evals/evals.json

Workflow

  1. State objective, success observation, engagement/scope reference, dates, and accountable owner.
  2. List in-scope synthetic assets or explicitly authorized targets; list exclusions and non-goals.
  3. Assign requester, approver, operator, exercise control, adjudicator, and escalation roles.
  4. Record allowed actions, prohibited actions, data handling, communications, and runtime controls.
  5. Define expiry, stop triggers, restart authority, evidence fields, and unresolved decisions.
  6. Mark live execution blocked and the plan offline-only when required runtime support is absent; never imply production readiness.
  7. Restart requires both current authorization and verified host enforcement of scope. Owner approval, risk acceptance, documented exceptions, or proposed compensating controls cannot waive either prerequisite; unverified alternatives keep the live lane blocked.

Rules

  • Plan only; do not include payloads, attack commands, credentials, real targets, or destructive steps.
  • Treat production modifications as separately approved actions.
  • Reuse authorization, evidence, and mapping.
  • Use primary framework sources; mark uncertain mappings explicitly. Plan evidence fields explicitly: engagement_scope_ref, skill_version, source, observed_at, finding_status, evidence_refs, limitations, and accountable_owner.

Anti-Patterns

  • No implied authorization: A completed plan is not approval.
  • No vague scope: Name boundaries and exclusions.
  • No hidden runtime dependency: State unsupported controls and block live work.
  • No team-color shortcut: Roles do not replace authorization.

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-engagement-planning of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/engagement-brief.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Cyber Engagement Planning 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 Engagement Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cyber Engagement Planning this skillHoangNguyen0403/agent-skills-standard572—~681Automated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
K8s Security PoliciesCybereason-Public/owLSM28012 repos~2kAutomated safety check: PassGPL-2.0
Payloadpayloadcms/payload45k5 repos~6.2kAutomated safety check: PassMIT
Convex Setup Authspokvulcan/poker-planning1158 repos~1.8kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed

  • K8s Security Policies

    Cybereason-Public/owLSM

    Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.

    280 GitHub starsUsed in 12 repos~2k tokens
    Backend & APIsAuto-check passed

  • Payload

    payloadcms/payload

    A skill your agent uses when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API).

    45k GitHub starsUsed in 5 repos~6.2k tokens
    Backend & APIsAuto-check passed

  • Convex Setup Auth

    spokvulcan/poker-planning

    Sets up Convex auth, identity mapping, and access control. An agent skill from spokvulcan/poker-planning.

    115 GitHub starsUsed in 8 repos~1.8k tokens
    Backend & APIsAuto-check passed

  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed

  • Abp Authorization

    abpframework/abp

    ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.

    14k GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed

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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    Auto-check passed

  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

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

    572 GitHub stars~743 tokensUpdated 2 days ago
    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 2 days ago
    Auto-check passed

Categories

Questions about Cyber Engagement Planning

What does Cyber Engagement Planning do?

Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Cyber Engagement Planning is an agent skill from HoangNguyen0403/agent-skills-standard. Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates.

When should I use Cyber Engagement Planning?

Cyber Engagement Planning fits situations like: preparing an exercise; assessment plan before execution.

How do I install Cyber Engagement Planning in Claude Code?

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

How do I install Cyber Engagement Planning in Codex?

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

Can I use Cyber Engagement Planning 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-engagement-planning -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-engagement-planning, .gemini/skills/cyber-engagement-planning, .github/skills/cyber-engagement-planning and .opencode/skills/cyber-engagement-planning in your project.

What does Cyber Engagement Planning need to run?

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

Does Cyber Engagement Planning 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 Engagement Planning 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 Engagement Planning use?

Cyber Engagement Planning 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 Engagement Planning use?

About 681 tokens (SKILL.md is roughly 2.7k 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 218 tokens, read only when the agent opens those files.

What are the alternatives to Cyber Engagement Planning?

Skills that share tags, products or a category with Cyber Engagement Planning: Configuring Horizon (coollabsio/coolify, 63k stars), K8s Security Policies (Cybereason-Public/owLSM, 280 stars), Payload (payloadcms/payload, 45k stars) and Convex Setup Auth (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cyber Engagement Planning?

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.