torusguard 2.0.0-alpha → 2.1.1

package/skills/torusguard/payload/workflows/apply.md

@@ -1,16 +1,14 @@
 ---
 description: Governed patch application with pre-apply rollback snapshots and Human Gate authorization.
-tools: Read, Grep, Glob, Bash, Edit, Write
-version: 1.4.0
+tools: Read, Grep, Glob, Bash, Edit, Write, run_command
+version: 2.0.0
 agent: remediator
 lifecycle-phase: Phase 5 (Patch Application)
 required-skills:
   - torusguard-apply
 scripts-binding:
-  - .torusguard/scripts/apply_runner.py
-  - .torusguard/scripts/report_sync.py
-  - .torusguard/scripts/run_manager.py
-  - .torusguard/scripts/diff_guard.py
+  - internal/apply/apply.go
+  - cmd/torusguard/main.go
 ---
 
 # /torusguard apply — Governed Patch Application & Rollback Snapshot
@@ -20,91 +18,62 @@ $ARGUMENTS
 ---
 
 ## Objective
-Governed patch application with pre-apply rollback snapshots and Human Gate authorization.
+Safely apply approved remediation bundles to disk source files, creating an automated byte-for-byte pre-apply backup snapshot (`.bak`) in `.torusguard/snapshots/<run_id>/`, asserting syntax validity, and distilling passing patterns into Golden Fix Recipes.
 
-Supported CLI flags:
-- `npx torusguard apply [--target <dir>]` : Apply candidate patches with confirmation prompt
-- `npx torusguard apply --diff` : Preview unified diffs without modifying files on disk
-- `npx torusguard apply --selective` : Interactively review and approve patches one by one
-- `npx torusguard apply --verify` : Trigger immediate differential AST recheck post-apply
-- `npx torusguard apply --list-snapshots` : List available historical pre-apply backup snapshots
-- `npx torusguard apply --yes` / `-y` : Non-interactive auto-approval mode
+---
+
+## Tri-Mode Execution
+
+| Mode | Command / Tool | Execution Method |
+| :--- | :--- | :--- |
+| **Mode A: Terminal CLI** | `torusguard apply candidate.patch [--yes]` | Shell execution of patch applier with snapshot creation. |
+| **Mode B: AI Chat Slash** | `/torusguard apply` | Guided conversational application with explicit Human Gate approval. |
+| **Mode C: Native MCP Tool** | Autonomous Agent Flow | Formulates patch with `torusguard_harden`, awaits Human Gate, invokes CLI. |
 
 ---
 
 ## Mandatory Pre-Flight Context Inspection
 
 Inspect bundle validity and file safety before modifying disk code:
-1. **Bundle Verification:** Assert `patch.diff` exists in active run's remediation folder.
-2. **Pre-Apply Snapshot:** Save a byte-for-byte backup copy (`.bak` or `.torusguard/snapshots/<run_id>/`) prior to editing.
+1. **Bundle Verification:** Assert `candidate.patch` or semantic `patch.json` exists.
+2. **Pre-Apply Snapshot:** Save a byte-for-byte backup copy (`.torusguard/snapshots/<run_id>/<rel_path>.bak`) prior to editing.
 3. **Uncommitted Changes:** Check git status; ensure target file has clean baseline.
 4. **Ponytail Check:** Re-verify that patch additions $\le 35$ and deletions $\le 25$.
 5. **Human Gate:** Confirm operator approval before committing edits to disk.
-6. **Workspace Cleanliness:** Verify git working tree has no uncommitted merge conflicts.
-7. **Execution Privilege:** Verify write access to targeted file locations.
-
----
-
-## When to Use /torusguard apply
-
-| Trigger Scenario | Recommended Action |
-| :--- | :--- |
-| Applying an approved remediation patch to disk | Run `/torusguard apply` |
-| Generating patch diff without modifying disk | Run `/torusguard harden` |
-| Verifying that patch eliminated flaw without regression | Run `/torusguard recheck` |
-| Reverting an applied patch | Restore from `.bak` snapshot |
-| Checking workspace status | Run `/torusguard status` |
 
 ---
 
 ## Living Report Invariant
 - Applied patches create pre-apply `.bak` snapshots in `.torusguard/snapshots/<run_id>/`.
 - Finding statuses transition in `security_report.md` to `APPLIED 🔵`.
-- Instant rollback available via `npx torusguard rollback`.
-
-## Execution Steps
-
-1. **Load Remediation Bundle:** Read `patch.diff` and metadata from active run directory.
-2. **Audit Patch Invariants:** Run `python .torusguard/scripts/diff_guard.py <patch.diff>`.
-3. **Create Rollback Backup:** Copy target file to `.torusguard/runs/<run_id>/.torusguard/snapshots/<run_id>/<filename>.bak`.
-4. **Apply Minimal Diff:** Execute precise surgical edit using `replace_file_content` or `patch`.
-5. **Assert Syntax & Integrity:** Check that modified file compiles cleanly without syntax errors.
-6. **Log Application Ledger:** Record timestamp, original SHA-256, and patched SHA-256 in `apply-log.json`.
+- Instant rollback available via `torusguard rollback`.
 
 ---
 
-## Failure Recovery
-
-- **Syntax Error After Patch:** Instantly revert target file from `.bak` backup snapshot.
-- **Merge / Context Conflict:** Re-run `/torusguard harden` to regenerate diff against latest disk lines.
-- **Missing Backup File:** Do not apply patch if backup copy cannot be written.
-- **Halt Trigger:** Abort if git working tree is dirty on conflicting lines.
-
----
-
-## Hallucination Guard
+## Execution Steps
 
-- ❌ Never apply code changes without creating an exact pre-apply rollback backup first.
-- ❌ Never touch files not explicitly listed in the approved `patch.diff`.
-- ✅ Always verify syntax compilation immediately after modifying source files.
+1. **Load Remediation Bundle:** Read `candidate.patch` or `patch.json`.
+2. **Obtain Human Gate:** Confirm user approval to modify target source file.
+3. **Create Rollback Backup:** Capture `.bak` in `.torusguard/snapshots/<run_id>/`.
+4. **Apply Surgical Edit:** Run `torusguard apply <patch> --yes` or apply semantic reflection.
+5. **Assert Syntax & Integrity:** Check that modified file compiles cleanly (`go test ./...`, syntax lint).
+6. **Recommend Recheck:** Run `torusguard recheck` or `/torusguard recheck`.
 
 ---
 
 ## Output Card Format
 
 ```markdown
-### 🚀 TorusGuard Patch Application
-- **Finding Addressed:** `TG-XXX-HASH`
-- **File Patched:** `src/path/to/file.py`
-- **Rollback Backup:** `.torusguard/runs/<run_id>/.torusguard/snapshots/<run_id>/<file>.bak`
-- **Churn Applied:** +[Additions] / -[Deletions] lines
-- **Syntax Check:** PASSED (clean compile)
-- **Status:** APPLIED — run `/torusguard recheck` to verify fix
+### 🚀 TorusGuard Patch Applied Successfully
+- **Target File:** `src/path/to/file`
+- **Backup Snapshot:** `.torusguard/snapshots/<run_id>/<file>.bak`
+- **Rollback Command:** `torusguard rollback`
+- **Next Step:** Run `/torusguard recheck` to verify closure
 ```
 
 ---
 
 ## Next Steps
 
-1. Run `/torusguard recheck` to perform differential audit on the modified file.
-2. Run test suites to verify that business logic and regressions remain intact.
+1. Run `/torusguard recheck` or `torusguard recheck` to verify closure and zero regressions.
+2. If unexpected behavior occurs, run `torusguard rollback`.

package/skills/torusguard/payload/workflows/audit.md

@@ -1,55 +1,47 @@
 ---
-description: Static security AST scanning, stable line-shift invariant fingerprinting, root-cause clustering, and 0-100 confidence scoring.
-tools: Read, Grep, Glob, Bash, Write
-version: 1.4.0
+description: Taint-aware static security AST scanning, cross-file interprocedural dataflow, 86+ rules across 22 families, and 7-signal calibrated confidence scoring.
+tools: Read, Grep, Glob, Bash, Write, run_command
+version: 2.0.0
 agent: auditor
 lifecycle-phase: Phase 2 (Static Audit & Clustering)
 required-skills:
   - torusguard-audit
 scripts-binding:
   - .torusguard/scripts/audit_runner.py
-  - .torusguard/scripts/report_sync.py
-  - .torusguard/scripts/run_manager.py
   - .torusguard/scripts/finding_scorer.py
+  - .torusguard/core/cross_file_taint.py
+  - .torusguard/core/confidence.py
+  - .torusguard/core/incremental.py
 ---
 
-# /torusguard audit — Static Security Code Scan & Clustering
+# /torusguard audit — Deep Taint-Aware Static Security Code Scan & Clustering
 
 $ARGUMENTS
 
 ---
 
 ## Objective
-Static security AST scanning, stable fingerprinting, root-cause clustering, throughput telemetry, and 0-100 scoring.
-
-Supported CLI flags:
-- `npx torusguard audit [--target <dir>]` : Specify project root directory
-- `npx torusguard audit --watch` / `-w` : Continuous watch mode, re-scanning on file change
-- `npx torusguard audit --sarif` : Automatically export OASIS SARIF v2.1.0 log
-- `npx torusguard audit --severity <critical|high|medium|low>` : Floor filter for findings
+Execute deep taint-aware static AST analysis across polyglot project files, evaluate code against 86+ canonical security rules across 22 families, trace interprocedural source-to-sink dataflows, assign stable line-shift invariant fingerprints, cluster architectural root causes, synchronize findings with `security_report.md`, and score findings with auditable 7-signal evidence-chain confidence ratings.
 
 ---
 
-## Mandatory Pre-Flight Context Inspection
+## Tri-Mode Execution
 
-Inspect workspace prerequisites before launching static audit:
-1. **Init State (`torusguard.json`):** Assert repository is initialized.
-2. **Active Rules (`rules/active/`):** Confirm rule definitions exist.
-3. **Exclusions:** Assert `node_modules/`, `.venv/`, `dist/`, `.git/` are skipped.
-4. **Run Folder:** Allocate isolated folder in `.torusguard/runs/`.
-5. **Syntax Check:** Check for syntax errors before parsing ASTs.
+| Mode | Command / Tool | Execution Method |
+| :--- | :--- | :--- |
+| **Mode A: Terminal CLI** | `torusguard audit [--incremental] [--watch] [--json]` | Shell execution of TorusGuard audit engine. |
+| **Mode B: AI Chat Slash** | `/torusguard audit` | Conversational guided audit with bounded context inspection. |
+| **Mode C: Native MCP Tool** | `torusguard_audit` | Autonomous agent tool invocation via stdio JSON-RPC. |
 
 ---
 
-## When to Use /torusguard audit
+## Mandatory Pre-Flight Context Inspection
 
-| Trigger Scenario | Recommended Action |
-| :--- | :--- |
-| First-time scan of repository or new branch | Run `/torusguard audit` |
-| Pre-commit review and PR security checks | Run `/torusguard audit` |
-| Uninitialized project | Run `/torusguard init` first |
-| Live endpoint or runtime probing | Run `/torusguard web-validate` |
-| Differential check after patch | Run `/torusguard recheck` |
+Inspect workspace prerequisites before launching static audit:
+1. **Init State (`torusguard.json`):** Assert repository is initialized or run `torusguard init`.
+2. **Active Rules (`rules/`):** Confirm rule definitions exist across the 22 architectural families.
+3. **Exclusions:** Assert `node_modules/`, `.venv/`, `dist/`, `.git/` are skipped.
+4. **Syntax Check:** Check for syntax errors before parsing ASTs.
 
 ---
 
@@ -57,31 +49,19 @@ Inspect workspace prerequisites before launching static audit:
 - Audit discoveries automatically synchronize to `security_report.md` at workspace root.
 - Findings transition into `OPEN 🔴` status with stable invariant fingerprints.
 
-## Execution Steps
-
-1. **Allocate Run Folder:** Run `python .torusguard/scripts/run_manager.py create audit`.
-2. **Scan Codebase ASTs:** Match active rules against source trees.
-3. **Compute Stable Fingerprints:** Hash AST context to produce stable IDs.
-4. **Cluster Root Causes:** Group findings sharing identical sinks.
-5. **Score Confidence (0–100):** Run `python .torusguard/scripts/finding_scorer.py --run <run_dir>`.
-6. **Emit Artifacts:** Write `findings.md`, `findings.json`, and `summary.md`.
-
 ---
 
-## Failure Recovery
-
-- **Zero Rules Active:** Re-run `/torusguard init` to activate rules.
-- **AST Parse Error:** Log syntax error on malformed file, skip, and continue.
-- **Scorer Failure:** Ensure Python 3.10+; verify finding JSON structure.
-- **Halt Trigger:** Abort if run folder cannot be allocated or disk write fails.
-
----
-
-## Hallucination Guard
+## Execution Steps
 
-- ❌ Never invent finding IDs without AST line hashing.
-- ❌ Never flag test fixtures as critical security flaws.
-- ✅ Always calculate scores using `.torusguard/scripts/finding_scorer.py`.
+1. **Launch Audit Scan:**
+   - **Mode A (CLI):** Run `torusguard audit` (or `python .torusguard/scripts/audit_runner.py`). Use `--incremental` for fast diffs.
+   - **Mode B (Chat):** Parse AST sinks and trace sources to sinks using `core.taint_graph` and bounded context windows.
+   - **Mode C (MCP):** Call `torusguard_audit` with `{"target": "."}`.
+2. **Scan Codebase ASTs:** Match 86+ canonical rules across 22 families against source trees.
+3. **Trace Taint Dataflows:** Follow untrusted inputs from sources to dangerous sinks across module boundaries.
+4. **Compute Stable Fingerprints:** Hash AST context to produce stable line-shift invariant IDs (`TG-XXX-<hash12>`).
+5. **Cluster Root Causes:** Group findings into the 22 canonical architectural root causes.
+6. **Synchronize Ground Truth:** Update `security_report.md` at workspace root.
 
 ---
 
@@ -89,12 +69,12 @@ Inspect workspace prerequisites before launching static audit:
 
 ```markdown
 ### 🔎 TorusGuard Static Audit Results
-- **Run ID:** `run-YYYYMMDD-HHMMSS-audit`
-- **Files Scanned:** [Count] source files
+- **Files Scanned:** [Count] source files ([Changed] changed)
+- **Taint Paths Confirmed:** [Count] verified dataflows
 - **Total Findings:** [Count] ([Critical] Critical, [High] High)
 - **Root Cause Clusters:** [Count] architectural issues
-- **Confidence:** [Score]/100
-- **Artifact:** `.torusguard/runs/<run_id>/findings.md`
+- **Confidence:** [Score]/100 (Evidence-Chain Calibrated)
+- **Living Report:** `security_report.md`
 ```
 
 ---
@@ -102,4 +82,4 @@ Inspect workspace prerequisites before launching static audit:
 ## Next Steps
 
 1. Run `/torusguard verify` to validate exploitability and review evidence.
-2. Run `/torusguard harden` to generate minimal surgical remediation plans.
+2. Run `/torusguard harden` to generate minimal surgical remediation plans conforming to the Ponytail protocol (<= 35 additions, <= 25 deletions).

package/skills/torusguard/payload/workflows/authorize.md

@@ -1,14 +1,14 @@
 ---
 description: Legal scope definition, target ownership proof verification, and safety boundary enforcement for runtime validation.
-tools: Read, Grep, Glob, Bash, Write
-version: 1.3.6
+tools: Read, Grep, Glob, Bash, Write, run_command
+version: 2.0.0
 agent: reviewer
 lifecycle-phase: Phase 1 (Authorization Gate)
 required-skills:
   - torusguard-authorize
 scripts-binding:
-  - .torusguard/scripts/report_sync.py
-  - .torusguard/scripts/safety_gate.py
+  - internal/validate/validate.go
+  - cmd/torusguard/main.go
 ---
 
 # /torusguard authorize — Legal Scope & Safety Gate
@@ -18,7 +18,17 @@ $ARGUMENTS
 ---
 
 ## Objective
-Legal scope definition, target ownership proof verification, and safety boundary enforcement.
+Legal scope definition, target ownership proof verification, and safety boundary enforcement for runtime validation.
+
+---
+
+## Tri-Mode Execution
+
+| Mode | Command / Tool | Execution Method |
+| :--- | :--- | :--- |
+| **Mode A: Terminal CLI** | `torusguard authorize` | Interactive boundary setup and cryptographic token generation. |
+| **Mode B: AI Chat Slash** | `/torusguard authorize` | Conversational parameter collection and scope validation. |
+| **Mode C: Native MCP Tool** | Safety Gate Guard | Administrative gatekeeper ensuring strict safety boundaries before probes. |
 
 ---
 
@@ -27,52 +37,20 @@ Legal scope definition, target ownership proof verification, and safety boundary
 Inspect authorization parameters and environment safety before executing:
 1. **Config Record (`.torusguard/config/torusguard.json`):** Assert repository is initialized.
 2. **Current Scope (`.torusguard/config/scope.json`):** Inspect active allowed targets, paths, and TTL expiry.
-3. **Environment Classification:** Assert target is local or staging (`localhost`, `127.0.0.1`, `*.local`, `*.staging.*`). Production targets require explicit approval.
+3. **Environment Classification:** Assert target is local or staging (`localhost`, `127.0.0.1`, `*.staging.*`).
 4. **Destructive Guard:** Ensure state-changing operations (`DELETE`, bulk drops) remain blocked by default.
-5. **Ownership Proof:** Verify target ownership token or local process binding.
-6. **TTL Window:** Ensure authorization window does not exceed 24 hours.
-
----
-
-## When to Use /torusguard authorize
-
-| Trigger Scenario | Recommended Action |
-| :--- | :--- |
-| Preparing for live HTTP probes or API validation | Run `/torusguard authorize` |
-| Updating allowed hosts, path prefixes, or rate limits | Run `/torusguard authorize` |
-| Static-only security audit | Skip authorize; run `/torusguard audit` |
-| Checking active legal scope status | Run `/torusguard status` |
-| Expired authorization window | Re-run `/torusguard authorize` |
+5. **TTL Window:** Ensure authorization window does not exceed 24 hours.
 
 ---
 
 ## Execution Steps
 
-1. **Capture Scope Parameters:** Collect target URL, allowed paths, forbidden prefixes, and max request budget.
-2. **Validate Host Ownership:** Verify target is local or matches authorized test domains.
-3. **Invoke Safety Gate:**
-   ```bash
-   python .torusguard/scripts/safety_gate.py check --url <target_url>
-   ```
-4. **Write Scope File (`.torusguard/config/scope.json`):** Save authorized targets, valid TTL timestamp, and request rate caps.
-5. **Confirm Scope Binding:** Verify `.torusguard/config/scope.json` parses as valid JSON against schema.
-
----
-
-## Failure Recovery
-
-- **Unreachable Host:** Verify local server is running on the specified port.
-- **Production Target Warning:** If target resolves to an external production host, halt and request operator override.
-- **Malformed JSON:** Re-initialize `scope.json` from `.torusguard/schemas/auth-boundary.schema.json`.
-- **Halt Trigger:** Abort immediately if user provides wildcard target (`*`) or third-party domain.
-
----
-
-## Hallucination Guard
-
-- ❌ Never proceed with runtime probing without an explicit, valid `.torusguard/config/scope.json`.
-- ❌ Never authorize destructive HTTP methods (`DELETE`, `DROP`) under default non-destructive policy.
-- ✅ Always validate targets through `.torusguard/scripts/safety_gate.py`.
+1. **Trigger Authorization:**
+   - **Mode A (CLI):** Run `torusguard authorize`.
+   - **Mode B (Chat):** Collect target host URL and allowed prefixes.
+2. **Generate Token:** Persist cryptographic authorization token into `.torusguard/auth.json`.
+3. **Write Scope Record:** Persist authorized targets and expiration TTL into `.torusguard/config/scope.json`.
+4. **Confirm Readiness:** Prepare environment for `/torusguard web-validate`.
 
 ---
 
@@ -81,9 +59,8 @@ Inspect authorization parameters and environment safety before executing:
 ```markdown
 ### 🔒 TorusGuard Authorization Gate
 - **Target URL:** [Target Host or URL]
-- **Environment:** [Localhost / Staging / Container]
-- **Allowed Paths:** [Path prefixes or all authorized]
-- **Rate Limit:** [Max requests / concurrency limit]
+- **Environment:** [Localhost / Staging]
+- **Session TTL:** 24 Hours
 - **Scope File:** `.torusguard/config/scope.json`
 - **Status:** AUTHORIZED — ready for `/torusguard web-validate`
 ```
@@ -92,5 +69,5 @@ Inspect authorization parameters and environment safety before executing:
 
 ## Next Steps
 
-1. Run `/torusguard audit` to scan codebase for AST security vulnerabilities.
-2. Run `/torusguard web-validate` to begin safe, authorized endpoint validation.
+1. Run `/torusguard web-validate` to begin safe, authorized endpoint validation.
+2. Run `/torusguard audit` to scan codebase for AST vulnerabilities.

package/skills/torusguard/payload/workflows/container.md

@@ -0,0 +1,29 @@
+# /torusguard-container — Container & Docker Security Audit
+
+$ARGUMENTS
+
+---
+
+## Objective
+Detect and remediate container privilege escalation, root execution, docker socket exposure, and build-time secret injection across `Dockerfile`, `Containerfile`, and `docker-compose.yml` configurations.
+
+---
+
+## Tri-Mode Parity
+- **Mode A (Terminal CLI):** `torusguard container [target]`
+- **Mode B (AI Chat Slash Command):** `/torusguard container [target]`
+- **Mode C (Native MCP Tool):** `torusguard_container`
+
+---
+
+## Execution Steps
+
+1. **Discover Container Configurations:** Discover all Dockerfiles and compose YAML files in the workspace.
+2. **Execute Static Heuristic Audit:** Run `ScanContainerFiles` or `torusguard_container` against discovered files.
+3. **Assert Security Invariants:**
+   - Enforce non-root user declarations (`TG-CONT-001`).
+   - Block Docker daemon socket mounts (`/var/run/docker.sock`) (`TG-CONT-002`).
+   - Disallow `privileged: true` and unconfined seccomp profiles (`TG-CONT-003`).
+   - Ban build-time secrets in `ARG` or `ENV` directives (`TG-CONT-004`).
+4. **Formulate Surgical Patches:** Propose minimal diffs adding non-root users (`USER appuser`) and secret mounts within Ponytail bounds (≤35 additions, ≤25 deletions).
+5. **Synchronize Report:** Log all container findings in `security_report.md`.

package/skills/torusguard/payload/workflows/exploit-check.md

@@ -1,15 +1,14 @@
 ---
 description: Safe, bounded, single-step exploitability confirmation across 5 standard verification statuses.
-tools: Read, Grep, Glob, Bash, Write
-version: 1.3.6
+tools: Read, Grep, Glob, Bash, Write, run_command
+version: 2.0.0
 agent: validator
 lifecycle-phase: Phase 3c (Exploitability Check)
 required-skills:
   - torusguard-exploit-check
 scripts-binding:
-  - .torusguard/scripts/report_sync.py
-  - .torusguard/scripts/safety_gate.py
-  - .torusguard/scripts/finding_scorer.py
+  - internal/validate/validate.go
+  - cmd/torusguard/main.go
 ---
 
 # /torusguard exploit-check — Bounded Exploitability Confirmation
@@ -19,62 +18,43 @@ $ARGUMENTS
 ---
 
 ## Objective
-Safe, bounded, single-step exploitability confirmation across 5 standard verification statuses.
+Safe, bounded, single-step exploitability confirmation using inert canary tokens without data loss or weaponized execution.
 
 ---
 
-## Mandatory Pre-Flight Context Inspection
+## Tri-Mode Execution
 
-Inspect authorization parameters and probe safety constraints:
-1. **Scope Check (`scope.json`):** Assert endpoint is authorized.
-2. **Approved Probes:** Use benign canaries (SQLi math, HTML marker, unauth read).
-3. **Destructive Ban:** Strictly prohibit drops, DOS, or weaponized payloads.
-4. **Safety Gate:** Verify probe with `safety_gate.py` prior to dispatch.
-5. **Bound:** Limit to single non-destructive HTTP request per finding.
-6. **Audit Trail:** Inject `X-TorusGuard-AuthID` header on all outbound requests.
+| Mode | Command / Tool | Execution Method |
+| :--- | :--- | :--- |
+| **Mode A: Terminal CLI** | `torusguard exploit-check [--url <url>] [--finding <id>]` | Terminal execution of sentinel canary prober. |
+| **Mode B: AI Chat Slash** | `/torusguard exploit-check` | Conversational exploitability triage and status classification. |
+| **Mode C: Native MCP Tool** | Bounded Probe Engine | Safe probe execution guarded by inert tokens and safety gate. |
 
 ---
 
-## When to Use /torusguard exploit-check
+## Mandatory Pre-Flight Context Inspection
 
-| Trigger Scenario | Recommended Action |
-| :--- | :--- |
-| Confirming whether a flaw is practically exploitable | Run `/torusguard exploit-check` |
-| Upgrading Medium confidence finding to Confirmed | Run `/torusguard exploit-check` |
-| Verifying IDOR or tenant isolation boundaries | Run `/torusguard exploit-check` |
-| Routine endpoint header inspection | Run `/torusguard web-validate` |
-| Applying approved remediation patch | Run `/torusguard apply` |
+Inspect authorization parameters and probe safety constraints:
+1. **Scope Check (`scope.json`):** Assert endpoint is authorized.
+2. **Approved Probes:** Use benign canaries (SQLi math identity `' OR 1=1--`, HTML marker `<tg-canary-tag>`).
+3. **Destructive Ban:** Strictly prohibit drops, DOS, or weaponized payloads.
+4. **Bound:** Limit to single non-destructive HTTP request per finding.
+5. **Audit Trail:** Inject `X-TorusGuard-AuthID` header on all outbound requests.
 
 ---
 
 ## Execution Steps
 
-1. **Verify Authorization Scope:** Confirm target host and route in `scope.json`.
-2. **Select Safe Canary:** Choose inert mathematical sentinel or unauth GET.
-3. **Validate With Safety Gate:**
-   ```bash
-   python .torusguard/scripts/safety_gate.py check --url <target_url> --payload <canary>
-   ```
-4. **Dispatch Bounded Single Probe:** Send request with header `X-TorusGuard-AuthID`.
-5. **Classify Status:** Evaluate response against 5 outcomes: `Confirmed`, `Needs Review`, `Not Reproducible`, `Blocked by Controls`, `Out of Scope`.
-6. **Emit Artifacts:** Write `exploit-check.md` and update `findings.json`.
-
----
-
-## Failure Recovery
-
-- **Connection Refused:** Verify target server is running locally on port.
-- **Safety Gate Block:** If `Manual Only`, halt automated probe and request human review.
-- **Ambiguous Response:** Mark finding as `Needs Review`; never assume exploit without proof.
-- **Halt Trigger:** Abort if probe causes server 500 error or unexpected crash.
-
----
-
-## Hallucination Guard
-
-- ❌ Never classify a vulnerability as `Confirmed` without direct sentinel reflection.
-- ❌ Never execute brute force attacks or automated password spraying.
-- ✅ Always provide reproducible curl commands with redacted credentials.
+1. **Trigger Exploit Check:**
+   - **Mode A (CLI):** Run `torusguard exploit-check --url http://localhost:3000 --finding TG-SEC-001`.
+   - **Mode B (Chat):** Review response to inert canary probe.
+2. **Classify Status:** Evaluate response against 5 canonical outcomes:
+   - `Confirmed`: Canary reflected or secondary tenant data leaked.
+   - `Not Reproducible`: Endpoint responded with 401/403 or sanitized input.
+   - `Needs Review`: Ambiguous status code or incomplete response.
+   - `Blocked by Controls`: WAF or rate limiter stopped probe.
+   - `Out of Scope`: Target endpoint is not authorized.
+3. **Update Living Report:** Record outcome in `security_report.md`.
 
 ---
 
@@ -84,10 +64,8 @@ Inspect authorization parameters and probe safety constraints:
 ### 🎯 TorusGuard Exploitability Confirmation
 - **Target Route:** `[METHOD] /path`
 - **Finding ID:** `TG-XXX-HASH`
-- **Canary Used:** [Inert Math Sentinel / Unauth Read]
 - **Status:** [Confirmed / Not Reproducible / Blocked]
 - **Evidence:** [Response snippet demonstrating leak or block]
-- **Replay Curl:** `curl -X [METHOD] http://localhost:PORT/path ...`
 ```
 
 ---

package/skills/torusguard/payload/workflows/git-mine.md

@@ -0,0 +1,25 @@
+# /torusguard-git-mine — Git Repository & History Secret Mining
+
+$ARGUMENTS
+
+---
+
+## Objective
+Inspect local Git metadata, `.git/config` remotes, and historical commit logs to uncover leaked API tokens, private certificates, and sensitive credentials committed in previous revisions.
+
+---
+
+## Tri-Mode Parity
+- **Mode A (Terminal CLI):** `torusguard git-mine [target]`
+- **Mode B (AI Chat Slash Command):** `/torusguard git-mine [target]`
+- **Mode C (Native MCP Tool):** `torusguard_git_mine`
+
+---
+
+## Execution Steps
+
+1. **Verify Git Environment:** Verify target directory is a valid Git repository containing `.git/`.
+2. **Audit Remote Configurations:** Check `.git/config` for embedded basic auth credentials in remote origin URLs (`TG-GIT-002`).
+3. **Mine Commit Log Diffs:** Inspect the last 50 commits (`git log -p`) for added tokens, keys, and credentials (`TG-GIT-001`).
+4. **Audit Tracked Sensitive Files:** Ensure `.env`, private keys, and certificates are not tracked in git tree history (`TG-GIT-003`).
+5. **Report & Revoke:** Provide immediate provider revocation steps and commit log cleanup guidance in `security_report.md`.