
sentinelx-prime
Stage-aware security guidance for planning, risky implementation changes, review, and release checkpoints.
- version
- 1.0.0
- GitHub stars
- 38
Install
/plugin install sentinelx-prime@sentinelx-prime-devRun it inside Claude Code after adding the marketplace with /plugin marketplace add alicankiraz1/SentinelXPrime.
Contents
Discovered from sourceSkills 5
Security Plan Gap
Overview
Find missing security requirements before code exists. This skill turns design omissions into actionable plan additions.
When to Use
- writing a feature plan or architecture
- reviewing a spec before implementation starts
- breaking work into tasks that may cross trust boundaries or handle sensitive data
Workflow
- Read the current plan, spec, or task breakdown.
- Load
references/plan-gap-checklist.md. - Load
../shared/common-web-threats.md,../shared/finding-schema.md, and the relevant stack profile if known. - Produce a gap report with missing controls, risk scenarios, and suggested plan additions.
- End with a closing coverage note using the shared headings: Reviewed / Not reviewed / Assumptions / Tools run.
Guardrails
- Treat missing requirements as gaps, not confirmed vulnerabilities.
- Prefer concise, actionable additions over generic best-practice lists.
- Lower confidence when the stack or architecture is only partly defined.
- Treat this skill as the default planning-stage review pass when
sentinelx-primeinvokes it automatically.
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
- 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, andreferences/active-analysis.md. - Classify the stage as
plan,review,test-rig, oruncertain, and classify whether the current work crosses a risky-change threshold. - Resolve repo-local checkpoint guidance through
references/context-resolution.mdrather than assuming a relative../../AGENTS.mdpath. - For
plan, invoke../sentinelx-plan-gap/SKILL.mdautomatically. - For risky implementation work, ask once whether the user wants a read-only active analysis pass for the current scope. If they accept, collect scoped evidence through
references/active-analysis.md. If git-backed discovery is unavailable but shell reads still work for files already visible in context or explicitly named by the user, use a limited current-source fallback and note the limitation in assumptions. If they decline or shell/file evidence is unavailable, stay description-based and note the limitation in assumptions. - For risky implementation work, run a low-noise scoped risky-change review pass using
references/risky-change-review-pass-template.mdwith an enriched context pack when active analysis was allowed and available. - If a risky-change review pass returns no material concern, do not create a separate interruption.
- For
review, ask once before invoking../sentinelx-review-gate/SKILL.md. If the user accepts, treat that acceptance as consent for read-only active analysis within the current review scope. - For
test-rig, ask once before invoking../sentinelx-test-rig/SKILL.md. - Normalize findings using
../shared/finding-schema.md. - End substantial outputs with a coverage note.
Stage Fallback
- If the stage is
uncertain, stay advisory, do not trigger a risky-change review pass, do not imply a full review occurred, and wait for stronger stage evidence or explicit user intent.
Guardrails
- Never claim the project is secure.
- Never run tools or mutate files without explicit user consent.
- Treat read-only active analysis as tool execution that still requires explicit user consent.
- If the stack is unclear, load
../shared/common-web-threats.mdand say the stack is uncertain. - Do not repeat the same offer after a clear refusal in the same stage.
- Do not imply that a child agent was spawned unless the user explicitly asked for delegation and the active environment actually supports that flow.
- Never send the full session history when a narrow scoped context pack is sufficient for the risky-change review pass.
- Risky-change review passes must remain advisory-only unless the user explicitly asks for stronger gating.
- If repo-local checkpoint policy is missing, do not imply that later-stage security offers are guaranteed automatically.
Security Review Gate
Overview
Run an advisory-only security review after implementation. This skill reports findings but does not block progress by default.
When to Use
- the user says the code is done or ready for review
- a feature was just implemented and needs a security pass
- a delivery or release checkpoint is approaching and source-level review would help
Workflow
- Ask once whether the user wants a focused security review, following
../sentinelx-prime/references/interaction-model.mdfor language behavior when available. - If the user declines, stop and do not repeat the same offer in the same stage.
- If the user accepts, treat that acceptance as consent for read-only active analysis within the current review scope and load
references/review-categories.md. - If git and shell access are available, inspect changed code within the current repo-local scope using
../sentinelx-prime/references/active-analysis.md. If git-backed active analysis is unavailable but shell reads still work, you may inspect files already visible in context or explicitly named by the user as a limited current-source fallback. If shell access is unavailable, stay description-based and note the fallback in assumptions. - Load
../shared/common-web-threats.md,../shared/finding-schema.md, and a stack profile when relevant. - Report findings using the required fields from
../shared/finding-schema.md. Includeevidence_sourcewhenever code, diff, heuristic, or description evidence materially affected the conclusion. - End with a closing coverage note using the shared headings: Reviewed / Not reviewed / Assumptions / Tools run.
Guardrails
- Do not block the user's progress automatically.
- Do not call heuristic review output a scan result unless a real tool was run.
- Do not equate no findings with security completeness.
- Do not describe limited current-source fallback as diff-grounded active analysis.
- Do not inspect code outside the accepted review scope just because it shares security-related keywords.
- Do not hardcode a fixed English ask prompt in this skill.
Security Test Rig
Overview
Offer a recommendation-only security check plan after implementation. This skill helps users set up the next validation step without silently provisioning anything.
When to Use
- a feature or project is approaching release or handoff
- the user wants a lightweight hardening or validation pass
- the next useful step is tool selection rather than source review
Workflow
- Ask once whether the user wants a stack-aware security check plan, following
../sentinelx-prime/references/interaction-model.mdfor language behavior when available. - If the user declines, stop and do not repeat the same offer in the same stage.
- If the user accepts, load
references/tool-selection.mdandreferences/sample-commands.md. - Recommend tools, commands, and checklist items based on the stack.
- End the recommendation with a closing coverage note using the shared headings: Reviewed / Not reviewed / Assumptions / Tools run.
- State clearly that no environment was provisioned and no tooling was installed automatically.
Guardrails
- Recommendation-only in v1.
- No installation, config mutation, CI wiring, or environment provisioning.
- Avoid presenting optional tools as mandatory without context.
- Do not hardcode a fixed English ask prompt in this skill.
Using SentinelXPrime
Overview
SentinelXPrime is a stage-aware security skill suite. Use it to add lightweight, advisory-first security structure without pretending to certify security.
Skill Map
sentinelx-prime: route the current conversation to the right security stagesentinelx-plan-gap: planning-stage security gap analysissentinelx-review-gate: opt-in post-implementation security reviewsentinelx-test-rig: opt-in security test/check planning before release
Operating Rules
- Keep the suite advisory-first unless the user explicitly asks for stronger gating.
- Do not claim the repository is secure, fully reviewed, or production-ready.
- Do not repeat the same review or test-rig offer after the user declines it in the current stage.
- Treat authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust-boundary work as the risky implementation threshold.
- Separate reviewed areas, unreviewed areas, assumptions, and tools run in substantial outputs.
Bootstrap
- Use this skill to remind the assistant that SentinelXPrime exists in the current session.
- When the stage is already clear, prefer the more specific SentinelXPrime skill instead of repeating this bootstrap.
Stage Hints
- If the code is done and the next question is whether the implementation is safe enough, prefer
sentinelx-review-gate. - If the work is moving into release, handoff, or hardening checks, prefer
sentinelx-test-rig. - If stage evidence is weak or contradictory, stay advisory and let
sentinelx-primeclassify the work asuncertain.
Hooks 1
Sponsors
Details
- Marketplace
- alicankiraz1/SentinelXPrime
- Author
- Alican Kiraz
- Category
- Community