Best use case
results is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
View the most recent security scan results without re-running the scan
Teams using results should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/results/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How results Compares
| Feature / Agent | results | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
View the most recent security scan results without re-running the scan
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Security Results Display the most recent security scan report. ## Step 1: Check for Results Look for `.security/report.md` in the project root. If it exists, read and display the full report. If it does not exist, display: ``` No security scan results found. Run /security:scan to perform a security assessment. ``` ## Step 2: Show Report Age Check the file modification time: ```bash stat -c %Y .security/report.md 2>/dev/null || stat -f %m .security/report.md 2>/dev/null ``` Display: "Last scan: [relative time ago]" If the report is older than 24 hours, suggest: "Results are over 24 hours old. Consider running `/security:scan` for fresh results." ## Step 3: Display Report Read and display `.security/report.md` in its entirety.
Related Skills
Example Skill
Brief description of what this skill does and the domain expertise it provides.
vulnerability-patterns
Index of vulnerability detection pattern skills. Routes to core patterns (universal) and language-specific patterns for security scanning.
vuln-patterns-languages
Language-specific vulnerability detection patterns for JavaScript/TypeScript, Python, Go, Java, Ruby, and PHP. Provides regex patterns and grep commands for common security vulnerabilities.
vuln-patterns-core
Universal vulnerability detection patterns applicable across all programming languages. Includes hardcoded secrets, SQL/command injection, path traversal, and configuration file patterns.
scan
Run a security assessment using deterministic static analysis tools with LLM-powered triage
remediation-library
Index of security remediation skills. Routes to specialized skills for injection, cryptography, authentication, and configuration vulnerabilities.
remediation-injection
Security fix patterns for injection vulnerabilities (SQL, Command, XSS). Provides language-specific code examples showing vulnerable and secure implementations.
remediation-crypto
Security fix patterns for cryptographic vulnerabilities (weak algorithms, insecure randomness, TLS issues). Provides language-specific secure implementations.
remediation-config
Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.
remediation-auth
Security fix patterns for authentication and authorization vulnerabilities (credentials, JWT, deserialization, access control). Provides language-specific secure implementations.
fix
Fix or guide remediation for a specific security finding from the latest scan report
baseline
Create or update the project security baseline, profile, suppressions file, and gitignore entries for security scans