sentinelx-prime

name

sentinelx-prime

description

Use when a repository wants stage-aware cybersecurity guidance during planning, risky implementation changes across authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust boundaries, post-implementation review, or pre-release hardening; do not trigger for doc-only, naming-only, formatting-only, or UI-only changes that do not affect a trust boundary

SentinelXPrime

Overview

Thin orchestrator for stage-aware security guidance. It chooses the right security skill for the current project stage and keeps outputs consistent.

When to Use

• planning a feature, architecture, or task breakdown
• changing authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, or another trust boundary
• finishing implementation and deciding whether to run a security review
• preparing release, handoff, or hardening checks

When Not to Use

• doc-only changes
• naming-only refactors
• formatting-only edits
• UI-only changes that do not affect a trust boundary

Workflow

1. Read references/context-resolution.md, references/activation-rules.md, references/interaction-model.md, references/risky-change-signals.md, references/notification-policy.md, references/lifecycle-persistence.md, and references/active-analysis.md.
2. Classify the stage as plan, review, test-rig, or uncertain, and classify whether the current work crosses a risky-change threshold.
3. Resolve repo-local checkpoint guidance through references/context-resolution.md rather than assuming a relative path.