Deepsec Documentation Guide
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
A skill your agent uses when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the report
Install Finding Discipline
$ npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hypnguyen1209/offensive-claude finding-discipline --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/finding-discipline .claude/skills/finding-discipline && rm -rf skills-srcUse ~/.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/
Install the "finding-discipline" agent skill from https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-discipline into .claude/skills/finding-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-discipline", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-disciplineType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hypnguyen1209/offensive-claude finding-discipline --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/finding-discipline .agents/skills/finding-discipline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "finding-discipline" agent skill from https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-discipline into .agents/skills/finding-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-discipline", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hypnguyen1209/offensive-claude finding-discipline --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/finding-discipline .cursor/skills/finding-discipline && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "finding-discipline" agent skill from https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-discipline into .cursor/skills/finding-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-discipline", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hypnguyen1209/offensive-claude.git --path skills/finding-discipline--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hypnguyen1209/offensive-claude finding-discipline --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/finding-discipline .gemini/skills/finding-discipline && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "finding-discipline" agent skill from https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-discipline into .gemini/skills/finding-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-discipline", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hypnguyen1209/offensive-claude finding-disciplineInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/finding-discipline .github/skills/finding-discipline && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "finding-discipline" agent skill from https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-discipline into .github/skills/finding-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-discipline", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hypnguyen1209/offensive-claude finding-discipline --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/finding-discipline .opencode/skills/finding-discipline && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "finding-discipline" agent skill from https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/finding-discipline into .opencode/skills/finding-discipline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-discipline", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
finding-discipline- GitHub stars
- 388
- Token cost
- ~1.1k tokens
- SKILL.md length
- 569 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the report
- Works in 3 steps: Set the structured proof signal and run → Pass it through the REQUIRED… → Only a [CONFIRMED] survivor goes in the…
- About to record
- SKILL.md covers Overview, The three tiers, The proof bar (per class) and Required mechanical gate, plus 4 more sections
- Calls python
What it does
Finding Discipline is an agent skill from hypnguyen1209/offensive-claude. Use when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the report
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security. The repository describes itself as: Offensive security toolkit for Claude Code covering red team, exploit dev, AD attacks, EDR bypass, mobile pentest. The licence is MIT.
When your agent uses it
- About to record
- Rate the severity of
- Report any security finding — before marking anything [CONFIRMED]
- Writing it into the report
Example prompts
- “/finding-discipline”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Set the structured proof signal and run
- Pass it through the REQUIRED finding-validator agent (PASS / KILL / DOWNGRADE).
- Only a [CONFIRMED] survivor goes in the report. Severity must match what was demonstrated (CVSS honest).
What it can do on your machine
Read from SKILL.md and the folder at commit a506ad3. 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
Shell commands in SKILL.md call:
python
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
Finding Discipline loads about 1.1k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 569 words of instructions outside code blocks.
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 hypnguyen1209/offensive-claude at commit a506ad3, republished under its MIT licence (© hypnguyen1209). 569 words, ~1,052 tokens.
Download SKILL.mdSave it as
.claude/skills/finding-discipline/SKILL.md (or your agent's skills folder).- name
- finding-discipline
- description
- Use when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the report
Finding Discipline
Overview
The Iron Law: No [CONFIRMED] without proof. A finding is a claim about real, demonstrated
impact — not a status code, a reflected string, or a hunch. This is the offensive equivalent of
test-driven development: the proof is the test, and the finding does not exist until it passes.
Violating the letter of this rule is violating its spirit.
The three tiers
[CONFIRMED]— impact demonstrated AND grounded in an evidence artifact that exists on disk.[POSSIBLE]— reachable but the class proof bar is not yet met. Keep digging; do not report as real.[INFO]— true but no security impact at the claimed severity.
The proof bar (per class)
A status code is not impact. See skills/references/finding-evidence-standards.md:
SSRF needs the internal response; IDOR needs another principal's data; RCE needs command output;
XSS needs script execution; open redirect needs an external destination.
Required mechanical gate
Before any finding is recorded or reported:
- Set the structured proof signal and run
python skills/vulnerability-analysis/scripts/validate_findings.py --findings f.json --evidence ./evidence— it rejects ungrounded findings and per-class false positives. - Pass it through the REQUIRED
finding-validatoragent (PASS / KILL / DOWNGRADE). - Only a
[CONFIRMED]survivor goes in the report. Severity must match what was demonstrated (CVSS honest).
See skills/references/finding-validation-runtime.md for the 7-question gate.
Read-first, never name-guess
If a function calls another, read the callee — do not infer what it does from its name.
sanitize(), is_safe(), validate_input() are exactly where vulnerabilities hide; a name is a
claim by the author, not evidence. The same applies to a config key, a decorator, or a CVE title:
open the thing before you reason about it. An unread dependency in a data-flow claim is a hole.
Quote-grounded confidence tiers
Every claim in a finding carries a confidence grounded in what you can quote, not in how it feels:
- High — a direct quote from the artifact (the exact source line, the response body, the decompiled instruction) supports the claim.
- Medium — an explicitly stated assumption bridges a gap you could not directly observe. State the assumption; do not hide it.
- Low — an inference you are flagging as unverified. Acceptable to record, never to report as fact.
This is orthogonal to the [CONFIRMED]/[POSSIBLE]/[INFO] tier (which is about impact); confidence
is about how well-grounded the claim is. A High-confidence claim of a Low-impact bug is still Low.
Show full SKILL.md (185 more words)Show less
Red Flags — STOP, downgrade to [POSSIBLE]
- "I'm sure it's exploitable" (but haven't shown impact)
- "The payload reflected, so it's XSS" / "I got a 200, so it works"
- "The DNS callback fired" (SSRF with no internal response)
- "I changed the id and got data" (but it was my own — self-IDOR)
- "It probably works on a real target" (default-deployment unproven)
All of these mean: it is [POSSIBLE], not [CONFIRMED]. Get the evidence.
Rationalizations
| Excuse | Reality |
|---|---|
| "Pattern-matched, clearly vulnerable" | Pattern ≠ exploit. Demonstrate impact or it's POSSIBLE. |
| "I'll attach evidence later" | No artifact on disk = ungrounded = REJECTED now. |
| "Blind RCE counts" | No output / no OOB confirmation = POSSIBLE, not CONFIRMED. |
| "Severity is obviously Critical" | CVSS must reflect demonstrated impact, not the worst case. |
| "The validator is overkill here" | Untested findings are how false positives ship. Run it. |
"The function is called sanitize, so it's safe" | A name is the author's claim, not proof. Read the callee. |
| "The solver timed out, so it's not exploitable" | A tool limit is feasibility:null (manual), never false. |
A short list of CONFIRMED findings beats a long list of POSSIBLEs. Killing a false positive is success.
© hypnguyen1209, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/finding-discipline of hypnguyen1209/offensive-claude.
Open the folder on GitHubat commit a506ad3
Compare with similar skills
Finding Discipline 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Finding Discipline this skillhypnguyen1209/offensive-claude | 388 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Skill Scannergetsentry/skills | 1k | 4 repos | ~2.5k | Automated safety check: Warn | Apache-2.0 | |
| Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit | 481 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 | |
| Shiro Attack CLISummerSec/ShiroAttack2 | 2.6k | — | ~945 | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
- Official
Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
Cve Remediation
rundeck/rundeck
Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.
More from hypnguyen1209/offensive-claude
All 9 skills in this repoCrypto Analysis
hypnguyen1209/offensive-claude
A skill your agent uses when assessing cryptography — TLS/PKI auditing, RSA/ECC key attacks, ECDSA nonce lattice recovery, symmetric/AEAD misuse, JWT/JOSE forgery, hash cracking, post-quantum…
Incident Response
hypnguyen1209/offensive-claude
A skill your agent uses when responding to or forensically investigating an incident — triage acquisition (Velociraptor/KAPE), Volatility 3 memory forensics, Chainsaw/Hayabusa EVTX timelining…
Malware Analysis
hypnguyen1209/offensive-claude
A skill your agent uses when reverse-engineering or detecting malware — static triage + capa/YARA-X, emulation/DBI/.NET unpacking, dynamic/fileless/Volatility 3 memory analysis, C2 config extraction…
Recon Osint
hypnguyen1209/offensive-claude
A skill your agent uses when mapping a target's external attack surface or gathering OSINT — subdomain enumeration, attack-surface mapping (httpx/katana/JS secrets), subdomain takeover…
Threat Hunting
hypnguyen1209/offensive-claude
A skill your agent uses when hunting threats or engineering detections — ATT&CK Detection-Strategies, Sigma + correlation with Detection-as-Code CI, Windows endpoint hunting…
Threat Model Discipline
hypnguyen1209/offensive-claude
A skill your agent uses when starting an engagement, before exploitation, or whenever the attack surface changes — build/validate the threat model and detect drift (new unreviewed surface) before…
Related
Categories
Questions about Finding Discipline
What does Finding Discipline do?
A skill your agent uses when about to record, claim, rate the severity of, or report any security finding — before marking anything [CONFIRMED] or writing it into the report. Finding Discipline is an agent skill from hypnguyen1209/offensive-claude.
When should I use Finding Discipline?
Finding Discipline fits situations like: about to record; rate the severity of; report any security finding — before marking anything [CONFIRMED]; writing it into the report.
How do I install Finding Discipline in Claude Code?
Run `npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a claude-code`. Or copy the skill folder (skills/finding-discipline in hypnguyen1209/offensive-claude) into .claude/skills/finding-discipline in your project. Claude Code loads it when a task matches its description.
How do I install Finding Discipline in Codex?
Run `npx skills add hypnguyen1209/offensive-claude --skill finding-discipline -a codex`. Or copy the skill folder (skills/finding-discipline in hypnguyen1209/offensive-claude) into .agents/skills/finding-discipline in your project. Codex loads it when a task matches its description.
Can I use Finding Discipline 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 hypnguyen1209/offensive-claude --skill finding-discipline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finding-discipline, .gemini/skills/finding-discipline, .github/skills/finding-discipline and .opencode/skills/finding-discipline in your project.
What does Finding Discipline need to run?
Going by SKILL.md and its folder, Finding Discipline needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Finding Discipline 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 Finding Discipline 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 Finding Discipline use?
Finding Discipline 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 Finding Discipline use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Finding Discipline?
Skills that share tags, products or a category with Finding Discipline: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars), Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars) and Security Alert Triage (elastic/agent-skills, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finding Discipline?
hypnguyen1209 (a GitHub user) maintains it in hypnguyen1209/offensive-claude, which has 388 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 28, 2026.
Source: hypnguyen1209/offensive-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.