chore: remove hightower skill (moved to farhoodliquor/skills)

This commit is contained in:
Test User
2026-04-22 00:04:33 +00:00
parent 84ae0f986d
commit 0013776646
-129
View File
@@ -1,129 +0,0 @@
---
name: hightower
version: "1.0.0"
description: "Interact with the Hightower pentest API — start scans, check status, retrieve reports. Hightower is a K8s-deployed penetration testing platform. Use when you need to run a security scan, check scan progress, or retrieve findings. Do NOT use for the domain work itself — only for scan orchestration."
allowed-tools: Bash, Read
---
# Hightower: Penetration Testing API
Hightower is deployed in the `hightower` namespace on the cpfarhood Kubernetes cluster. It exposes a REST API for scan management and a Temporal cluster for workflow orchestration.
## API Endpoint
**Internal (from within K8s):** `http://hightower-api.hightower:3000`
**External:** Requires `kubectl port-forward -n hightower svc/hightower-api 3000:3000`
**Authentication:** Bearer token via `HIGHTOWER_API_TOKEN` env var.
---
## Common Operations
### List all scans
```bash
curl -s -H "Authorization: Bearer $HIGHTOWER_API_TOKEN" \
"$HIGHTOWER_API_URL/api/scans"
```
### Start a new scan
```bash
curl -s -X POST "$HIGHTOWER_API_URL/api/scans" \
-H "Authorization: Bearer $HIGHTOWER_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"targetUrl": "https://example.com",
"gitUrl": "https://github.com/user/repo",
"workspace": "my-workspace"
}'
```
Response: `{ "id": "hightower-worker-abc123", "workspace": "my-workspace", "status": "running" }`
### Get scan status by workspace name
```bash
curl -s -H "Authorization: Bearer $HIGHTOWER_API_TOKEN" \
"$HIGHTOWER_API_URL/api/scans?workspace=my-workspace"
```
The `workspace` filter returns all jobs for that workspace. Look for `status: "completed"` or `status: "running"`.
### Get scan report
```bash
curl -s -H "Authorization: Bearer $HIGHTOWER_API_TOKEN" \
"$HIGHTOWER_API_URL/api/scans/{workspace}/report"
```
Returns the full markdown report. Use `workspace` name, not job ID.
### Cancel a running scan
```bash
curl -s -X POST "$HIGHTOWER_API_URL/api/scans/{id}/cancel" \
-H "Authorization: Bearer $HIGHTOWER_API_TOKEN"
```
---
## Environment Variables
| Variable | Value | Description |
|----------|-------|-------------|
| `HIGHTOWER_API_URL` | `http://hightower-api.hightower:3000` | Hightower REST API base URL |
| `HIGHTOWER_API_TOKEN` | Token from hightower-credentials secret | Bearer auth token |
---
## Report Format
The report is a markdown file with the following structure:
```
# Comprehensive Security Assessment Report
## Executive Summary
- Assessment Date: YYYY-MM-DD
- Target: https://example.com
- Model: MiniMax-M2.7
## Findings
### [CRITICAL|HIGH|MEDIUM|LOW] Title
- **Location:** URL or code reference
- **Description:** ...
- **PoC:** ...
- **Remediation:** ...
```
## Parsing Findings
Extract findings by looking for `### [SEVERITY]` headers:
```bash
# Extract all finding titles and severities
grep -E "^### \[(CRITICAL|HIGH|MEDIUM|LOW)\]" report.md
# Extract CRITICAL and HIGH findings only
grep -A 10 "^### \[CRITICAL\]" report.md
grep -A 10 "^### \[HIGH\]" report.md
```
## Scan Lifecycle
1. **running** — Job is active, worker processing
2. **completed** — Job succeeded, report available at `{workspace}/report`
3. **failed** — Job failed (check pod logs)
Typical runtime: ~36 minutes for a full 13-agent pipeline.
---
## Notes
- The MCP server on port 3100 is deprecated — use the REST API directly
- Reports are private to the cluster (PVC); fetch via the API
- For Paperclip issues from findings, parse the report and create issues via the Paperclip API