Pi Security

ingest-markdown-report

Submit one security report to Pi from inline Markdown and a .md or .markdown filename after tenant verification and fresh explicit confirmation. Reject attachments, local files, links, and binaries.

investigate-finding

Investigate Pi Security findings by listing, locating, explaining, summarizing, or comparing exact FND-XXX IDs, UUIDs, or Pi finding URLs. Read-only; use when the user needs evidence about a Pi finding.

remediation-guidance

Fetch existing Pi remediation guidance for a finding or vulnerable package, and optionally prepare one missing package plan after tenant verification and fresh explicit confirmation. Use when guidance is needed without code changes.

review-security-posture

Review Pi Security posture by combining threat-model application context with Code Gatekeeper pull-request and issue records. Read-only; use for tenant posture, coverage, and prioritization questions.

secure-development-playbook

Retrieve Pi secure-development guidance once for a stable engineering task, reconcile its coverage with current repository evidence, and submit targeted feedback only after tenant verification and fresh explicit confirmation.

security-design-review

Start one Pi Security design review from a supported Confluence or Notion URL or inline Markdown after tenant verification and fresh explicit confirmation. Reject attachments, local files, and binaries.