AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Secret Guard

skill-kissrosecicd-hub-agents-evolution-pr-prep-secret-guard · by kissrosecicd-hub

Mandatory secret scanning before any git operation. MUST trigger automatically before git commit, git push, git add, PR creation, or any commit-related skill. Scans staged files for API keys, tokens, credentials, and other secrets to prevent accidental exposure in version control.

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-kissrosecicd-hub-agents-evolution-pr-prep-secret-guard

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-kissrosecicd-hub-agents-evolution-pr-prep-secret-guard)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Secret Guard? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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 keys
  • credentials.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.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.