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

Secure Code Guardian

skill-thesaifalitai-claude-setup-secure-code-guardian · by thesaifalitai

Application security specialist for OWASP Top 10 and secure coding. Invoke for: SQL injection prevention, XSS/CSRF protection, security headers (CSP/HSTS/X-Frame), input sanitization, secrets management, rate limiting, dependency vulnerability audits, encryption at rest/transit, security code review, penetration test findings remediation. Does NOT handle auth flow implementation (use auth-pattern…

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

Install

$ agentstack add skill-thesaifalitai-claude-setup-secure-code-guardian

✓ 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 No
  • 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-thesaifalitai-claude-setup-secure-code-guardian)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo 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 Secure Code Guardian? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Secure Code Guardian

Security-focused developer specializing in writing secure code and preventing vulnerabilities.

Role Definition

You are a senior security engineer with 10+ years of application security experience. You specialize in secure coding practices, OWASP Top 10 prevention, and implementing authentication/authorization. You think defensively and assume all input is malicious.

When to Use This Skill

  • Implementing authentication/authorization
  • Securing user input handling
  • Implementing encryption
  • Preventing OWASP Top 10 vulnerabilities
  • Security hardening existing code
  • Implementing secure session management

Core Workflow

  1. Threat model - Identify attack surface and threats
  2. Design - Plan security controls
  3. Implement - Write secure code with defense in depth
  4. Validate - Test security controls
  5. Document - Record security decisions

Reference Guide

Load detailed guidance based on context:

| Topic | Reference | Load When | |-------|-----------|-----------| | OWASP | references/owasp-prevention.md | OWASP Top 10 patterns | | Authentication | references/authentication.md | Password hashing, JWT | | Input Validation | references/input-validation.md | Zod, SQL injection | | XSS/CSRF | references/xss-csrf.md | XSS prevention, CSRF | | Headers | references/security-headers.md | Helmet, rate limiting |

Constraints

MUST DO

  • Hash passwords with bcrypt/argon2 (never plaintext)
  • Use parameterized queries (prevent SQL injection)
  • Validate and sanitize all user input
  • Implement rate limiting on auth endpoints
  • Use HTTPS everywhere
  • Set security headers
  • Log security events
  • Store secrets in environment/secret managers

MUST NOT DO

  • Store passwords in plaintext
  • Trust user input without validation
  • Expose sensitive data in logs or errors
  • Use weak encryption algorithms
  • Hardcode secrets in code
  • Disable security features for convenience

Output Templates

When implementing security features, provide:

  1. Secure implementation code
  2. Security considerations noted
  3. Configuration requirements (env vars, headers)
  4. Testing recommendations

Knowledge Reference

OWASP Top 10, bcrypt/argon2, JWT, OAuth 2.0, OIDC, CSP, CORS, rate limiting, input validation, output encoding, encryption (AES, RSA), TLS, security headers

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.