Install
$ agentstack add skill-kissrosecicd-hub-agents-evolution-pr-prep-secret-guard ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Secret Guard
MANDATORY: Run before ANY git commit, push, add, or PR operation.
Scan Commands
Run these before proceeding with any git operation:
# Check for secret keywords in staged changes (skip removed lines)
git diff --cached | grep -iE '(client_secret|password|api[_-]?key|secret_key|private_key|token|bearer|credential)' | grep -v "^-" | head -20
# Check for long credential-like strings (base64, hex, Azure secrets with ~)
git diff --cached | grep -oE '[a-zA-Z0-9+/~]{35,}' | head -10
# Check config files specifically for secrets
git diff --cached -- '*.json' '*.yaml' '*.yml' | grep -iE '(secret|password|key|token)' | grep -v "^-" | head -10
# List staged files
git diff --cached --name-only
High-Risk Files
STOP and warn if any of these are staged:
.env,.env.*— Never commit.claude/settings.json— Often contains embedded secrets*.pem,*.key,*.p12,*.pfx— Private keyscredentials.json,secrets.json,auth*.json,*token*.json**/config/*.json— May contain hardcoded credentials
Secret Patterns
| Pattern | Identifier | |----------------------|-----------------------------------------| | Azure AD secrets | Contains ~ (e.g., Pl~8Q~abc...) | | AWS Access Keys | Starts with AKIA | | GitHub tokens | Starts with ghp_, gho_, ghs_ | | API keys | Prefixes: sk-, pk-, api_ | | JWT tokens | Starts with eyJ | | Base64 secrets | 40+ alphanumeric chars |
If Secrets Detected
BLOCK the git operation immediately.
Response format:
🚨 SECRET DETECTED - BLOCKING COMMIT
Found in:
Pattern:
REQUIRED ACTIONS:
1. Remove the secret from the file
2. Use environment variables instead
3. If already committed: rotate the credential immediately
Proceed with commit? (only after user confirms false positive)
Safe to Proceed When
- No secret keywords in staged diffs
- No high-risk files staged (or user explicitly reviewed)
- No long random strings resembling credentials
- User confirmed any flagged items are false positives
Post-Commit Reminder
After successful commit without pre-commit hooks installed: > "Consider adding a pre-commit hook for automatic secret scanning."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kissrosecicd-hub
- Source: kissrosecicd-hub/agents-evolution
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.