deep-scanner

Name: deep-scanner
Author: KnoxOps

38stars4forks

How to install deep-scanner?

knoxops/open-devops-skills/deep-scanner

$npx -y skills add KnoxOps/open-devops-skills --skill deep-scanner

Installs into the current project.

Summary

Phase 2 Deep Scanner — performs deep technical and business scanning on candidate machines approved by the user. One agent per machine, max 8 concurrent. Agent uses whatever tools available (SSH/cloud APIs).

Files · 1

View on GitHub

SKILL.md

1	## Input Parameters
2
3	\| Name \| Type \| Required \| Description \|
4	\|------\|------\|----------\|-------------\|
5	\| run_dir \| string \| Yes \| Workspace root directory \|
6	\| resource_id \| string \| Yes \| Single resource ID to scan \|
7	\| ssh_key_path \| string \| No \| SSH key path for remote access \|
8
9	## Execution Flow
10
11	### Task Context
12
13	Before starting execution, initialize `task_context.json`:
14
15	```json
16	{
17	"task_id": "<task_id from input>",
18	"current_step": 0,
19	"current_step_id": null,
20	"status": "running",
21	"steps": {
22	"deep_scan": "pending",
23	"review_deep_scan": "pending"
24	},
25	"updated_at": "<ISO timestamp>"
26	}
27	```
28
29	Update this file after each step completes. On error, set step status to `"failed"` and overall `status` to `"failed"`.
30
31	### Step 1: deep_scan
32
33	Type: agent
34	Description: Execute deep scan on target machine
35
36	## Execution
37	Launch an independent agent with the following prompt file:
38
39	Prompt file: `$PLUGINS/ico/skills/deep-scanner/prompts/deep-scan.agent.md`
40	Agent workflow:
41
42	1. Prepare the execution environment
43
44	2. Execute the agent with the prompt
45
46	3. Write results to:
47	- File: `analysis/deep_scan_{resource_id}.json`
48
49	## Output
50	- Schema: schemas/deep-scan.schema.json
51	- File: analysis/deep_scan_{resource_id}.json
52
53	### Progress Tracking
54
55	After completing this step, update `task_context.json`:
56	- Set `current_step_id` to `"deep_scan"`
57	- Set `steps.deep_scan` to `"completed"`
58	### Step 2: review_deep_scan
59
60	Type: inline
61	Description: Validate deep scan output before completing (BLOCKING)
62
63	## Execution
64	Follow these instructions:
65
66	Read all deep_scan output files and validate them before completing:
67
68	Each deep_scan_*.json MUST have:
69	- technical.processes[] (non-empty)
70	- technical.listening_ports[] (non-empty)
71	- technical.traffic_graph with edges[] array (iftop data collected)
72	- technical.crontab_entries[] present
73	- technical.systemd_timers[] present
74	- technical.disk_partitions[] present
75	- technical.external_traffic[] present (ss -tn output)
76	- business.owner with name, team fields
77	- business.application non-empty
78
79	Do NOT include ssh_key_path or any credential paths in output.
80	Fix any issues before completing. BLOCKING.
81
82
83	### Progress Tracking
84
85	After completing this step, update `task_context.json`:
86	- Set `current_step_id` to `"review_deep_scan"`
87	- Set `steps.review_deep_scan` to `"completed"`

People who liked this also viewed

6 picks

Type

deep-scanner

38stars4forks

View on GitHub

How to install deep-scanner?

knoxops/open-devops-skills/deep-scanner

$npx -y skills add KnoxOps/open-devops-skills --skill deep-scanner

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Input Parameters
2
3	\| Name \| Type \| Required \| Description \|
4	\|------\|------\|----------\|-------------\|
5	\| run_dir \| string \| Yes \| Workspace root directory \|
6	\| resource_id \| string \| Yes \| Single resource ID to scan \|
7	\| ssh_key_path \| string \| No \| SSH key path for remote access \|
8
9	## Execution Flow
10
11	### Task Context
12
13	Before starting execution, initialize `task_context.json`:
14
15	```json
16	{
17	"task_id": "<task_id from input>",
18	"current_step": 0,
19	"current_step_id": null,
20	"status": "running",
21	"steps": {
22	"deep_scan": "pending",
23	"review_deep_scan": "pending"
24	},
25	"updated_at": "<ISO timestamp>"
26	}
27	```
28
29	Update this file after each step completes. On error, set step status to `"failed"` and overall `status` to `"failed"`.
30
31	### Step 1: deep_scan
32
33	Type: agent
34	Description: Execute deep scan on target machine
35
36	## Execution
37	Launch an independent agent with the following prompt file:
38
39	Prompt file: `$PLUGINS/ico/skills/deep-scanner/prompts/deep-scan.agent.md`
40	Agent workflow:
41
42	1. Prepare the execution environment
43
44	2. Execute the agent with the prompt
45
46	3. Write results to:
47	- File: `analysis/deep_scan_{resource_id}.json`
48
49	## Output
50	- Schema: schemas/deep-scan.schema.json
51	- File: analysis/deep_scan_{resource_id}.json
52
53	### Progress Tracking
54
55	After completing this step, update `task_context.json`:
56	- Set `current_step_id` to `"deep_scan"`
57	- Set `steps.deep_scan` to `"completed"`
58	### Step 2: review_deep_scan
59
60	Type: inline
61	Description: Validate deep scan output before completing (BLOCKING)
62
63	## Execution
64	Follow these instructions:
65
66	Read all deep_scan output files and validate them before completing:
67
68	Each deep_scan_*.json MUST have:
69	- technical.processes[] (non-empty)
70	- technical.listening_ports[] (non-empty)
71	- technical.traffic_graph with edges[] array (iftop data collected)
72	- technical.crontab_entries[] present
73	- technical.systemd_timers[] present
74	- technical.disk_partitions[] present
75	- technical.external_traffic[] present (ss -tn output)
76	- business.owner with name, team fields
77	- business.application non-empty
78
79	Do NOT include ssh_key_path or any credential paths in output.
80	Fix any issues before completing. BLOCKING.
81
82
83	### Progress Tracking
84
85	After completing this step, update `task_context.json`:
86	- Set `current_step_id` to `"review_deep_scan"`
87	- Set `steps.review_deep_scan` to `"completed"`

People who liked this also viewed

6 picks

Type