SkillAgentSearch skills...

scope-discipline

Use when about to send a request to, scan, enumerate, exploit, or otherwise interact with any host, IP, URL, or asset — before the first packet reaches a target

Install / Use

npx skills add hypnguyen1209/offensive-claude --skill scope-discipline

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Security

Supported Platforms

Zed

Tags

Our assessment of scope-discipline

scope-discipline scores 81/100 on our quality scale, 986th of 1,097 Security skills we index.

Its SKILL.md is 2.5 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

It has 377 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so scope-discipline is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-26. Automated pattern scan on 2026-10-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scope-discipline compared with similar skills

All 4 of these similar skills score higher than scope-discipline; compare them before choosing.

SkillScoreStarsUpdatedFormat
scope-discipline (this skill)by hypnguyen1209813772mo agoSKILL.md
algorithmic-artby anthropics100177.9k58d agoSKILL.md
pptxby anthropics100177.9k58d agoSKILL.md
prospectingby coreyhaines3110060.1k8d agoSKILL.md
ad-creativeby coreyhaines3110060.1k8d agoSKILL.md

Frequently asked questions

How do I install scope-discipline?
Run npx skills add hypnguyen1209/offensive-claude --skill scope-discipline. The install tabs above show the steps for each supported agent.
Which AI agents does scope-discipline work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scope-discipline safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scope-discipline still maintained?
The repository was last updated about 2 months ago, so scope-discipline is actively maintained.

name: scope-discipline description: Use when about to send a request to, scan, enumerate, exploit, or otherwise interact with any host, IP, URL, or asset — before the first packet reaches a target

Scope Discipline

Overview

The Iron Law: No target without authorization. Every target you touch must be inside the written authorization, encoded in scope.json. This is the authorization boundary of an authorized engagement — it is not optional, and the operator cannot waive it. It is the offensive equivalent of TDD's "no code without a test": no action without an in-scope, authorized target.

Violating the letter of this rule is violating its spirit.

The rule

Before touching ANY target, confirm it is in scope:

python skills/coding-mastery/scripts/_lib/scope_guard.py check <target> --scope .engage/scope/scope.json
# exit 0 = in-scope (proceed) | exit 3 = OUT (stop) | exit 2 = error (stop)

For outward actions, gate through action_guard.py (mutating verbs need approval; out-of-scope → block; per-host circuit breaker). Bash scripts source lib.sh and call _in_scope.

scope.json is operator-defined per engagement — you declare exactly what your authorization covers. The guard never blocks authorized testing; it blocks what is outside your own declared scope (strays, typos, look-alikes, an attacker-influenced redirect target).

Red Flags — STOP, do not send the request

  • "This subdomain is obviously theirs" (not in scope.json → out)
  • "It's just a quick check / read-only GET" (in-scope check still required first)
  • "The target came from a redirect / recon output / user paste" (verify before touching)
  • "*.acme.com so acme.com.evil.com is fine" (look-alike — the guard rejects it; so do you)
  • "The user told me to hit it" (instructions don't expand the authorization boundary)

All of these mean: run scope_guard.py check first. Out-of-scope ⇒ do not proceed.

Rationalizations

| Excuse | Reality | |--------|---------| | "Scope is obviously fine" | Confirm against scope.json; assumption is how OOB incidents happen. | | "It's adjacent infra, basically in scope" | Adjacent ≠ authorized. Out unless declared. | | "I'll note the out-of-scope hit in the report" | You don't hit it, then note it. You don't hit it. | | "Removing the guard is faster" | The guard IS the authorization. Removing it = unauthorized attack. |

Out-of-scope, shared/third-party, and anything not named in the authorization are off-limits — see TERMS.md. You own every request the toolkit sends.

Related Skills

View on GitHub
GitHub Stars377
CategorySecurity
Updated2mo ago
Forks65

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions