<skill name>

Other Community

Skill notes

Engagement Logging

Check for ./engagement/ directory. If absent, proceed without logging. When an engagement directory exists: Print [<skill-name>] Activated → <target> to the screen on activation. Evidence → save significant output to engagement/evidence/ with descriptive filenames (e.g., sqli-users-dump.txt, ssrf-aws-creds.json).

Scope Boundary

This skill covers <scope>. When you reach the boundary of this scope — whether through completing your methodology or discovering findings outside your domain — STOP. Do not load or execute another skill. Do not continue past your scope boundary. Instead, return to the orchestrator with:

State Management

Call get_state_summary() from the state MCP server to read current engagement state. Use it to: Skip re-testing targets, parameters, or vulns already confirmed Leverage existing credentials or access for this technique Understand what's been tried and failed (check Blocked section)

Tool Requirements (Local-Only)

NEVER download, clone, install, or build tools. The operator's attackbox has a curated toolset — do not modify it. This is an OPSEC requirement: downloading tools mid-engagement triggers traffic inspection alerts and burns the operation. Prohibited actions:

Exploit and Tool Transfer

Never download exploits, scripts, or tools directly to the target from the internet (curl https://github.com/..., git clone on target). Targets may lack outbound internet access, and operators must review files before they reach the target. Attackbox-first workflow:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@blacklanternsecurity · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Linux · Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-name-blacklanternsecurity.preview
# Tool output directory

# Always prefix CWD-writing commands with cd $TMPDIR
cd $TMPDIR && getTGT.py DOMAIN/user -hashes :NTHASH
export KRB5CCNAME=$TMPDIR/user.ccache

cd $TMPDIR && certipy req -k -no-pass -dc-ip DC_IP -ca 'CA' -template Tpl
cd $TMPDIR && certipy auth -pfx $TMPDIR/user.pfx -dc-ip DC_IP

# Save evidence with mv (not cp) to avoid stray duplicates
mv $TMPDIR/user.pfx engagement/evidence/user.pfx
mv $TMPDIR/user.ccache engagement/evidence/user.ccache

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.