Menu
Parses a risks.md file and synchronizes it to the web app Report Risks DB (create/update). Reflects report id, name, points, and description.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AITU Final multi-AI manager. Use when one AI is coordinating multiple Codex/Claude workers, workers ask what to do next, report blocked/done/high-value findings, or the user wants one manager to assign next tasks without manually maintaining a long dispatcher prompt.
Pivot/Tunneling autonomous skill: automatic segment detection from a single pivot IP, automatic SSH credential attempts, tunnel establishment (ligolo/ssh/chisel), internal network host/port discovery, and automatic MCP reflection (add_host/update_host/import_scan_data).
Automatic Bug Bounty report generation. Collects MCP data from report_id, host_ip:port, or host_ip:port bug_type, generates Description, registers/updates via web app, and saves attachments.
Automatic Risk report generation. Auto-infers the target from a Report ID, risk name, or the current MCP attack chain context to generate a Description, register in the web app, and save attachments.
AITU Final autonomous orchestrator. Use when the user says continue, keep going, do the next thing, or gives no target context. Read MCP state, lock onto one active risk objective, and dispatch scanning, web, AD, pivot, SCADA, and reporting without asking the user to choose a host or risk.
AD autonomous attack (token-optimized): enum -> BH/Kerberos -> spray -> privesc -> DCSync. If no arguments are given, automatically selects the next domain/DC target from MCP and proceeds.
| name | update-risks |
| description | Parses a risks.md file and synchronizes it to the web app Report Risks DB (create/update). Reflects report id, name, points, and description. |
| argument-hint | [file_path] (default: docs/risks.md) |
Source file: $ARGUMENTS (if empty, docs/risks.md)
## <Risk Name>
- report id : <platform_report_id>
- Points: <number>
- Description: <text>
Each ## heading represents one Risk entry.
## :
## - report id : (trim)- Points: - Description: curl -s http://localhost:10000/api/report/risks
name as the key.For each parsed item:
If the same name already exists -> PATCH:
curl -s -X PATCH http://localhost:10000/api/report/risks/<db_id> \
-H "Content-Type: application/json" \
-d '{"reportId":"<reportId>","name":"<name>","description":"<description>"}'
If not -> POST:
curl -s -X POST http://localhost:10000/api/report/risks \
-H "Content-Type: application/json" \
-d '{"reportId":"<reportId>","name":"<name>","description":"<description>"}'
Output the processing results as a table:
| Action | Report ID | Name | Status |
|---------|-----------|---------------------|--------|
| Created | 10 | Domain Infra... | OK |
| Updated | 11 | SCADA: Brewery... | OK |
http://localhost:10000.