issues: Skill for Claude Code

.claude/skills/review-security/SKILL.md

review-security is a skill for Claude Code from vepo/issues. It costs 42 tokens per session (1,039 once invoked), scanned A, original, Apache-2.0.

A read-only review of an application's source code for security problems such as weak login permissions, unsafe input handling, exposed secrets, and cross-site scripting.

In plain words
What is it for?
Use it to audit a whole codebase or a selected area, including authentication, endpoints, browser code, configuration, and tests.
Why use it?
It helps find security weaknesses without changing the code. Each finding includes an explanation and a task describing how a developer can fix it.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths.

This is vepo/issues's own configuration. It tells Claude Code how to work on issues itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything issues configures →

View source ↗ vepo/issues
Reuse

Borrowing it

Nothing to install: this file belongs to vepo/issues. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vepo/issues/main/.claude/skills/review-security/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/vepo/issues

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-security

README.md
[![agentmods](https://agentmods.dev/badge/skills/vepo/issues/review-security/github.svg)](https://agentmods.dev/skills/vepo/issues/review-security)
Your own site
<a href="https://agentmods.dev/skills/vepo/issues/review-security"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-security/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-security

Your own site · 80×15
<a href="https://agentmods.dev/skills/vepo/issues/review-security"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,039 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01039
Opus 5.5 $0.00017 $0.00416
Sonnet 5.5 $0.00008 $0.00208
Haiku 4.5 $0.00004 $0.00104

Measured 1mo ago against content hash 8a343ef5222e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-security scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/review-security/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Security Audit agent for Issues running a full codebase security review. Act as described in .claude/agents/security-audit.md. Produce a read-only security audit — do not change application code. Teach developers how to fix each issue via Fix tasks in the report.

Prerequisites: Read SECURITY.md, ARCHITECTURE.md (JWT and endpoint security), and skim auth packages under src/main/java/dev/vepo/issues/auth/.

Scope

Default: entire application surface:

  • src/main/java/dev/vepo/issues/ (all endpoints, services, repositories)
  • src/main/webui/ (guards, interceptors, token storage, rich-text, uploads)
  • src/main/resources/ (application*.properties, Flyway, keys references)
  • src/test/ only when tests disable security meaningfully or embed secrets

If the user names a package, path, or recent diff, prioritize that but still scan cross-cutting auth and secrets.

Output

Write one report:

reports/security-audit-{sequential}-{dd-MM-yyyy-HH-mm-ss}.md

Severity: critical | high | medium | low | info.

Do not ask for confirmation before starting. Do not edit src/** in this command. Do not open PRs or commit.


Phase 1 — Inventory

  1. List *Endpoint classes; note @DenyAll / @RolesAllowed / @PermitAll / public auth paths.
  2. List Angular routes with/without authGuard (or equivalent).
  3. Note auth provider modes (AUTH_PROVIDER: local / ldap / endpoint) and JWT key configuration.
  4. Note file upload / CSV import entry points.

Phase 2 — Authentication

Check Pass criteria
Login / register / recovery Rate-limit or abuse notes if missing; tokens not predictable; no password in logs/responses
JWT Issuer/keys not weakened in prod profile; refresh not issuing for wrong principal
Token storage (SPA) No unnecessary persistence of secrets; interceptor attaches Bearer correctly
Password handling Hashing via configured PBKDF2 (or equivalent); no plaintext compare

Read the full file on GitHub · 116 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 116 lines · 42 tokens per session scan A 8a343ef5222e

Subscribe to this mod's changes

review-security is a skill published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,039 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.