Back to catalog
Human reviewedDevelopment

Skill dossier

secure-code-guardian

Source declaration

Use when implementing authentication/authorization, securing user input, or preventing OWASP Top 10 vulnerabilities — including custom security implementations such as hashing passwords with bcrypt/argon2, sanitizing SQL queries with parameterized statements, configuring CORS/CSP headers, validating input with Zod, and setting up JWT tokens. Invoke for authentication, authorization, input validation, encryption, OWASP Top 10 prevention, secure session management, and security hardening. For pre-built OAuth/SSO integrations or standalone security audits, consider a more specialized skill.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when implementing authentication/authorization, securing user input, or preventing OWASP Top 10 vulnerabilities — including custom security implementations such as hashing passwords with bcrypt/argon2, sanitizing SQL queries with parameterized statements, configuring CORS/CSP headers, validating input with Zod, and setting up JWT tokens. Invoke for authentication, authorization, input validation, encryption, OWASP Top 10 prevention, secure session management, and security hardening. For pre-built OAuth/SSO integrations or standalone security audits, consider a more specialized skill.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides implementing authentication, authorization, input validation and OWASP Top 10 defenses, with explicit validation checkpoints.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Models threats and plans security controls before coding.
  • Implements bcrypt or argon2 hashing, parameterized queries, Zod validation and JWT checks.
  • Configures rate limiting and security headers such as CSP and HSTS.
  • Tests brute-force protection, privilege escalation paths, injection payloads and header presence.

Limitations & scope

  • The skill itself says dedicated OAuth/SSO integrations and standalone audits may need a more specialized skill.
  • Examples are TypeScript and Node-centric.
  • Not a substitute for a professional security audit; none of the examples were run here.

Relevant for

  • Developers building login and session flows
  • Teams hardening an Express API
  • Engineers implementing input validation

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
23 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/secure-code-guardian/references/authentication.mdReference3.3 KB
skills/secure-code-guardian/references/input-validation.mdReference3.3 KB
skills/secure-code-guardian/references/owasp-prevention.mdReference3.3 KB
skills/secure-code-guardian/references/security-headers.mdReference2.9 KB
skills/secure-code-guardian/references/xss-csrf.mdReference3.1 KB
skills/secure-code-guardian/SKILL.mdInstruction7.1 KB

SKILL.md frontmatter

{
  "name": "secure-code-guardian",
  "description": "Use when implementing authentication/authorization, securing user input, or preventing OWASP Top 10 vulnerabilities — including custom security implementations such as hashing passwords with bcrypt/argon2, sanitizing SQL queries with parameterized statements, configuring CORS/CSP headers, validating input with Zod, and setting up JWT tokens. Invoke for authentication, authorization, input validation, encryption, OWASP Top 10 prevention, secure session management, and security hardening. For pre-built OAuth/SSO integrations or standalone security audits, consider a more specialized skill.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "security",
    "triggers": "security, authentication, authorization, encryption, OWASP, vulnerability, secure coding, password, JWT, OAuth",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "fullstack-guardian, security-reviewer, architecture-designer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Threat model

    Identify the attack surface and threats for the feature.

  2. 02
    Action

    Implement defense in depth

    Write secure code using hashing, parameterized queries, validation and token checks.

  3. 03
    Decision

    Run validation checkpoints

    Test brute-force protection, privilege escalation, injection payloads and headers/CORS after each step.

  4. 04
    Output

    Deliver secure implementation

    Provide code, security considerations, configuration requirements and testing recommendations.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

39 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
High

Credential or secret material is referenced

7 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

19 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Dynamic command execution is referenced

3 occurrences

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

10 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Have a security engineer review any auth, crypto and session code it generates, and verify secrets stay in environment variables.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/secure-code-guardian # .claude/skills/secure-code-guardian
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/secure-code-guardian/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md for secure-code-guardian is discoverable at the destination, then ask Claude Code to use it on a small test task.

Prerequisites

  • The skill itself says dedicated OAuth/SSO integrations and standalone audits may need a more specialized skill.
  • Examples are TypeScript and Node-centric.
  • Not a substitute for a professional security audit; none of the examples were run here.

Example prompts

Representative task

Use the secure-code-guardian skill to add login to this Express API: bcrypt hashing, Zod input validation, rate limiting, helmet headers and a 15-minute JWT in an httpOnly cookie. List the tests to confirm each control.

Inspect before use

Read the secure-code-guardian skill files at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/secure-code-guardian/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Lists concrete validation checkpoints for auth, authorization, input and headers.
  • Clear banned-practice list such as MD5, SHA-1 and hardcoded secrets.

Considerations

  • Security code needs expert review regardless of source.
  • Example choices like HS256 JWT may not fit your architecture.
Research conclusion

A helpful secure-coding checklist whose generated code should still go through human security review.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/secure-code-guardian
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.