@backbay-labs/security-review
ASecurity review for risky code changes
Install
agr install @backbay-labs/security-review --target claudeWrites 1 file into .claude/skills/, pinned to git-5e57d7a2.
- .claude/skills/security-review/SKILL.md
Document
description: "Security review for risky code changes"
Security Review
Security Checklist
Before proceeding with risky actions, use the clawdstrike_check MCP tool to verify policy compliance:
- Pre-flight check: Call
clawdstrike_checkwith the action_type and target before executing - Secret scanning: Verify no secrets, API keys, or credentials are being written to files
- Dependency audit: For new dependencies, check for known vulnerabilities
- Permission scope: Ensure file operations stay within allowed paths
- Shell safety: Validate shell commands against the ShellCommandGuard policy
Action Type Mapping
Use these action_type values when calling clawdstrike_check:
| Scenario | action_type | target |
|---|---|---|
| Writing/reading files | file | Absolute file path |
| Running shell commands | shell | The command string |
| HTTP/network requests | egress | Domain or URL |
| Installing packages | shell | Install command |
| MCP tool invocation | mcp_tool | Tool name |
Response Guidelines
When this skill is active:
- Proactively call
clawdstrike_checkbefore file writes to sensitive paths - Flag potential security issues with severity levels (Critical/High/Medium/Low)
- Suggest safer alternatives when an action would be blocked by policy
- Reference specific guards that would evaluate the action
Recommended Tools
Use these MCP tools in order of priority when this skill activates:
| Tool | When to Use |
|---|---|
clawdstrike_check | Before any file write, shell command, or egress -- the primary enforcement tool |
clawdstrike_policy_eval | To test hypothetical actions without executing them -- use for planning |
clawdstrike_policy_show | To understand which guards are active and what the current restrictions are |
clawdstrike_scan | To audit all MCP server configs for misconfigurations before a review |
clawdstrike_policy_lint | To validate policy YAML files for syntax/schema errors |
Guard Reference
These guards are evaluated during checks:
- ForbiddenPathGuard - Blocks access to sensitive filesystem paths
- PathAllowlistGuard - Enforces allowlist-based path access
- SecretLeakGuard - Detects secrets/credentials in file content
- ShellCommandGuard - Blocks dangerous shell commands
- EgressAllowlistGuard - Controls outbound network access
- PatchIntegrityGuard - Validates patch/diff safety
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-5e57d7a2f0f22026-07-31