Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Zyrexnn/Cybermesnpx agentmods add commands/zyrexnn/cybermes/scopeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/zyrexnn/cybermes/scope)<a href="https://agentmods.dev/commands/zyrexnn/cybermes/scope"><img src="https://agentmods.dev/badge/commands/zyrexnn/cybermes/scope/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/zyrexnn/cybermes/scope"><img src="https://agentmods.dev/badge/commands/zyrexnn/cybermes/scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00568 |
| Opus 5.5 | $0.00000 | $0.00227 |
| Sonnet 5.5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
scope scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to scope — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: scope description: Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...]
/scope
The mandatory pre-flight gate. Verify a host or URL is in scope before any
active testing. Scope is enforced in code (engine/scope.py), not by LLM
judgment — deny wins, default deny.
What This Does
- Loads in-scope / out-of-scope patterns from the engagement's
scope.md(thehuntscaffold creates it) or from inline patterns. - Checks each asset deterministically with
engine/scope.py:- apex
acme.com→ the apex and any subdomain *.acme.com→ any subdomain (NOT the bare apex)api.acme.com→ that exact host10.0.0.0/8→ any IP in the CIDRre:^lab[0-9]+\.acme\.io$→ explicit regex (prefixre:)
- apex
- Prints
IN-SCOPE/OUT-OF-SCOPE <reason>and exits non-zero if any asset is out of scope — so it can gate automation.
Usage
/scope api.acme.com
/scope api.acme.com staging.acme.io admin.acme.com
Under the hood, run the deterministic checker directly:
# Against the engagement scope.md (preferred — fill scope.md from the program page first)
python3 engine/scope.py api.acme.com --md ~/Targets/acme/scope.md
# Or with inline patterns (repeat --in-scope / --out-of-scope per pattern)
python3 engine/scope.py api.acme.com evil.com \
--in-scope acme.com --in-scope '*.acme.io' --out-of-scope admin.acme.com
Rules
- Run this before any HTTP touch. An
OUT-OF-SCOPEresult is a hard stop — do not probe the asset. - If
scope.mdis still the empty template ((paste ... here)placeholders), fill it from the program page first; an empty in-scope list = default-deny = everything rejected, which is the safe default. - Deny wins: if an asset matches both an in-scope and an out-of-scope rule, it is out of scope.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 52 lines · 0 tokens per session scan A 4117d3273843
scope is a command published in the GitHub repository Zyrexnn/Cybermes (668 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 568 tokens. A static security scan graded it A with 0 findings. It is 100% identical to scope, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
sicario.assess
Assess the repository against SicarioSpec guardrails.
sicario.review
Review the active spec, plan, tasks, staged changes, or branch for security and governance gaps.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.