Phalanx runs parallel-fork CVE remediation on a GitHub repository. Paste a repo URL, and the skill detects critical CVEs in the dependency tree, forks the dependency state N ways via Ghost, validates each hypothesis in isolated InsForge backends, cancels false positives mid-flight via Redis Pub/Sub, converts the Dockerfile to a Chainguard zero-CVE base, and publishes a signed evidence chain to cited.md. Use when the user asks to scan a repository for vulnerabilities, remediate a CVE autonomously, generate an SBOM with attestation, or produce a legally-defensible security remediation record. Also use for keywords like "CVE", "supply chain attack", "dependency audit", "zero-day remediation", "SBOM", "Sigstore", or "security remediation."

Put an approved Senso draft live where AI models can cite it, and follow what happens to it. Use for publishing generated content ("publish this", "make it live", "push it to citeables"), checking or retrying where it went ("did it publish", "retry the failed one"), pulling it back ("unpublish", "take it down"), and for what happened after — citations, which prompts a page is winning, and the provenance audit of a live URL. Also destinations and the call-to-action card. The publish step of senso-verification-loop. Not for writing or checking content — that is senso-generate-verify.