Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/vepo/issues/review-securitynpx skills add vepo/issues --skill review-securitygit clone --depth 1 https://github.com/vepo/issuesWrote 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.
[](https://agentmods.dev/skills/vepo/issues/review-security)<a href="https://agentmods.dev/skills/vepo/issues/review-security"><img src="https://agentmods.dev/badge/skills/vepo/issues/review-security.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00042 | $0.01039 |
| Opus 5 | $0.00021 | $0.00519 |
| Sonnet 5 | $0.00008 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
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 4d 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.
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
- List
*Endpointclasses; note@DenyAll/@RolesAllowed/@PermitAll/ public auth paths. - List Angular routes with/without
authGuard(or equivalent). - Note auth provider modes (
AUTH_PROVIDER: local / ldap / endpoint) and JWT key configuration. - 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 |
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.
- 4d ago First seen · 116 lines · 42 tokens per session scan A 8a343ef5222e
review-security is a skill published in the GitHub repository vepo/issues (8 stars, last pushed 1mo 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. 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.
Other skills, from other repositories
review-pending-pr-reviews
Review, grill, edit, and post pending PR review drafts saved by /review-pr (or its batch/cron runners). Lists drafts that have not yet been posted, walks the maintainer through each finding, then posts, closes, or discards. Use when the user says "post my pending reviews", "what reviews are waiting", "go through the…
nx-generate
Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nxdocs or…
docs-website-update
Sync docs commits from master out to the live docs branches in the nx repo: cherry-picks docs( / feat(nx-dev) commits onto website- AND the latest . .x release branch. Use when "update the docs branch", "update nx.dev", "push the latest docs changes out", "cherry-pick docs commits", "sync website-23", "ship docs to…
nx-gradle-plugin-version-bump
Bump the dev.nx.gradle.project-graph plugin version. Use when updating the Gradle project graph plugin version across the codebase, creating the migration files, and updating migrations.json.
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
fact-check
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation.