security-baseline

Name: security-baseline
Availability: InStock
Author: jmagar

Audits changed files for nine-point security baseline and generates prioritized reports.

Updated Aug 23, 2026

Search Tags:#security #oauth #jwt #rust #csp #baseline #csrf

Ready to run

npx skills add https://github.com/jmagar/rust-bin --skill security-baseline-jmagar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-baseline
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/security-baseline
Command: npx skills add https://github.com/jmagar/rust-bin --skill security-baseline-jmagar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoritative security baseline checks sourced from spec.md § Security baseline. Covers CSP, OAuth callback, PKCE, JWKS, /api/v1/log CSRF, /mcp auth parity, stdio MCP, redact_url, and backtrace policy. Preloaded by security-reviewer.

Core Features & Use Cases

Validates critical web and API security controls (CSP headers, OAuth flow integrity, PKCE, JWTs/JWKS, CSRF protection) across a Rust-based stack.
Applies the nine-check baseline to changed files and surfaces HIGH-severity blockers for releases and audits.
Generates actionable remediation guidance and an auditable report for developers, reviewers, and security teams.

Quick Start

Inspect the project and run the security baseline checks to verify CSP, OAuth, PKCE, JWKS, and backtrace policy compliance.

Frequently Asked Questions about security-baseline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce secure defaults for CSP, OAuth, and JWT in a Rust application?▼

Secure defaults in a Rust app are enforced by auditing code against a nine-point security baseline covering CSP, OAuth, PKCE, JWKS, and CSRF, then flagging HIGH severity items as blockers. A structured report with remediation suggestions is generated for review.

What security checks should I run on changed Rust files before a release?▼

Run a nine-point baseline audit on changed files to validate CSP, OAuth, PKCE, JWKS, /api/v1/log CSRF, MCP auth parity, redact_url, and backtrace policies. HIGH severity violations are flagged as blockers to prevent insecure releases.

Does this baseline audit validate PKCE and JWKS configuration for OAuth flows?▼

Yes, the baseline audit explicitly validates OAuth flow integrity by checking PKCE and JWKS configurations. It ensures these critical authentication controls are correctly implemented before generating a machine-readable report of violations.

How do I generate a machine-readable security report for Rust code reviews?▼

Generate a machine-readable security report by applying the nine-check baseline to changed files. The output highlights specific violations and provides prioritized remediation suggestions suitable for both automation and human reviewer analysis.

What is the best way to check MCP auth parity and backtrace policies in Rust?▼

Check MCP auth parity and backtrace policies by running the baseline audit, which includes these specific checks alongside CSP and OAuth validation. The audit enforces secure configuration and surfaces violations in a structured report.