Individual skill
pentest-task-tree
Iterative PTT (Penetration Testing Tree) session reasoning — model evidence, alternative mechanisms, and prerequisites without prescribing an engagement lifecycle.
packages/decepticon/decepticon/skills/standard/decepticon/pentest-task-tree/SKILL.md
Source commit df879550544d36b6b1e69062f05adae28537adf2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 6,567
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- cybersecurity Repository topic
- hacking Repository topic
- langchain Repository topic
- langgraph Repository topic
- llm Repository topic
- generative-ai Repository topic
- pentesting Repository topic
- pentest Repository topic
- security Derived category
- testing Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Evidence-backed hypothesis trees
A tree can organize alternative mechanisms and their prerequisites. It is an
analysis representation, not an execution plan or a mandated pentest lifecycle.
Root nodes name the security question; children identify necessary conditions,
competing explanations or concrete observations. Link every observed node to its
source and keep proposed tests distinct from results.
## Modeling constraints
Use identifiers stable enough to retain provenance when an assumption changes.
A child is relevant only when it can change the parent conclusion. Avoid invented
services, ports or account privileges. Record contradicted nodes and why they were
refuted rather than deleting the evidence. A closed/filtered observation at one time