skeeper: Skill for Claude Code

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

security-review is a skill for Claude Code from compozy/skeeper. It costs 61 tokens per session (2,839 once invoked), scanned A, a copy of security-review, MIT.

A code-security review process that looks for exploitable weaknesses such as injection, cross-site scripting, authentication, authorization, and cryptography problems. It traces attacker-controlled data through the code before reporting an issue.

In plain words
What is it for?
Use it to review a file, code change, or codebase for high-confidence security vulnerabilities and report their severity.
Why use it?
It reduces false alarms by checking whether a suspicious pattern can actually be reached and exploited in the project.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is compozy/skeeper's own configuration. It tells Claude Code how to work on skeeper 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 skeeper configures →

Reuse

Borrowing it

Nothing to install: this file belongs to compozy/skeeper. 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/compozy/skeeper/main/.agents/skills/security-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/compozy/skeeper

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 security-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/compozy/skeeper/security-review/github.svg)](https://agentmods.dev/skills/compozy/skeeper/security-review)
Your own site
<a href="https://agentmods.dev/skills/compozy/skeeper/security-review"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/security-review/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 security-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/compozy/skeeper/security-review"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,839 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00061 $0.02839
Opus 5.5 $0.00024 $0.01136
Sonnet 5.5 $0.00012 $0.00568
Haiku 4.5 $0.00006 $0.00284

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

Security

Grade A, and why

security-review scanned grade A with 2 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get(f"{settings.SEER_AUTOFIX_URL}{path}")

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

child_process.exec(user) # Node.js
Origin

This is a copy

100% identical to security-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/security-review/SKILL.md · 313 lines

How it starts

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

Security Review Skill

Identify exploitable security vulnerabilities in code. Report only HIGH CONFIDENCE findings—clear vulnerable patterns with attacker-controlled input.

Scope: Research vs. Reporting

CRITICAL DISTINCTION:

  • Report on: Only the specific file, diff, or code provided by the user
  • Research: The ENTIRE codebase to build confidence before reporting

Before flagging any issue, you MUST research the codebase to understand:

  • Where does this input actually come from? (Trace data flow)
  • Is there validation/sanitization elsewhere?
  • How is this configured? (Check settings, config files, middleware)
  • What framework protections exist?

Do NOT report issues based solely on pattern matching. Investigate first, then report only what you're confident is exploitable.

Confidence Levels

Level Criteria Action
HIGH Vulnerable pattern + attacker-controlled input confirmed Report with severity
MEDIUM Vulnerable pattern, input source unclear Note as "Needs verification"
LOW Theoretical, best practice, defense-in-depth Do not report

Do Not Flag

General Rules

  • Test files (unless explicitly reviewing test security)
  • Dead code, commented code, documentation strings
  • Patterns using constants or server-controlled configuration
  • Code paths that require prior authentication to reach (note the auth requirement instead)

Server-Controlled Values (NOT Attacker-Controlled)

These are configured by operators, not controlled by attackers:

Source Example Why It's Safe
Django settings settings.API_URL, settings.ALLOWED_HOSTS Set via config/env at deployment
Environment variables os.environ.get('DATABASE_URL') Deployment configuration
Config files config.yaml, app.config['KEY'] Server-side files
Framework constants django.conf.settings.* Not user-modifiable
Hardcoded values BASE_URL = "https://api.internal" Compile-time constants

Read the full file on GitHub · 313 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 · 313 lines · 61 tokens per session scan A 6d36fa39ada8

Subscribe to this mod's changes

security-review is a skill published in the GitHub repository compozy/skeeper (89 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 2,839 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). It is 100% identical to security-review, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens