deadeye-vapt

deadeye-vapt is a skill for Claude Code from deepaksinghcs14/deadeye-cc. It costs 48 tokens per session (6,397 once invoked), scanned B, original, MIT.

A source-code security assessment that examines a whole service as an attacker would, covering web, API, and AI-related risks. It finds reachable attack paths without sending traffic, running exploits, or checking hosts and cloud systems.

In plain words
What is it for?
Use it to inspect a repository's attack surface, assess OWASP web, API, and large-language-model risks, and rank findings from most serious to least serious.
Why use it?
It can reveal old routes, missing access checks, and other vulnerabilities that a review of recent code changes may miss. It provides the code-based part of a penetration test while leaving live-system testing out of scope.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: mentions Claude Code.

Part of the deadeye plugin — 10 skills, 3 commands, 7 hooks shipped together

Good fit Use it to inspect a repository's attack surface, assess OWASP web, API, and large-language-model risks, and rank findings from most serious to least serious.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/deepaksinghcs14/deadeye-cc/deadeye-vapt
Install

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.

Any agent
npx skills add deepaksinghcs14/deadeye-cc --skill deadeye-vapt
Clone the repo
git clone --depth 1 https://github.com/deepaksinghcs14/deadeye-cc

Made for: Claude Code.

Or install deadeye, the plugin that ships this one along with the rest of its 10 skills, 3 commands, 7 hooks.

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 deadeye-vapt

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/deepaksinghcs14/deadeye-cc/deadeye-vapt"><img src="https://agentmods.dev/badge/skills/deepaksinghcs14/deadeye-cc/deadeye-vapt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,397 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00048 $0.06397
Opus 5 $0.00024 $0.03198
Sonnet 5 $0.00010 $0.01279
Haiku 4.5 $0.00005 $0.00640

Measured today against content hash cfd518198a51, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

deadeye-vapt scanned grade B 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 today.

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.

Downloads and executes remote codemediumSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

| `dep:` | vulnerable or superseded dependency, unpinned CI action ref, mutable `:latest` base image, `curl \| sh` installer, LLM03 supply chain |

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

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

| `dep:` | vulnerable or superseded dependency, unpinned CI action ref, mutable `:latest` base image, `curl \| sh` installer, LLM03 supply chain |
skills/deadeye-vapt/SKILL.md · 448 lines

How it starts

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

Deadeye VAPT

A whole-service vulnerability assessment and penetration test, static and whitebox: find this service's real attack surface, then find what an attacker reaches through it. This is not a diff review. /deadeye-guard and /deadeye-review catch what changed; this catches what's already there — the endpoint nobody touched this session, the auth check that was never written, the route still live from an API version everyone thinks is retired.

What this is not. No traffic is sent, no exploit is run, nothing outside this repository's source is touched — no network probing, no host/container/cloud-IAM layer, no runtime fuzzing. This is the source half of a VAPT: a whitebox read that reasons like an attacker with the code in hand, not the network half. Say this plainly in the output, not just here.

How this runs. Phase 0 (the four surface tracks below) and the ambiguous-scope gate run first, sequentially, as normal interactive turns — Phase 0 is a handful of greps, no fan-out needed, and the ambiguity gate needs a live turn to actually ask from (a Workflow runs to completion in the background with no pause point to ask mid-script). Once scope is settled, on Claude Code, load the workflow-authoring skill and run the rest as a Workflow: Phase 1 (attack-surface inventory) fans out across whichever surface tracks Phase 0 confirmed, then Phase 3/4 (triage + verify) fan out one agent per tag-family, each grounded in the Phase 2 trust-boundary map printed below — then one integration pass over every returned finding before the report (Phase 5) is generated. This is the default, not an opt-in — a whole-service pass is already the heaviest, least-frequent command here, and it spends meaningfully more tokens than a single-agent pass to get meaningfully more coverage; say so if asked why. Every other host has no Workflow tool — run every phase below as one agent there, same as always.

Set each agent's tier explicitly in the script — a Workflow's agent() calls run outside deadeye's own routing advisory (that only watches the interactive Agent tool, not a script's internal calls), so an untiered script silently inherits the session's own model for every agent, tiering nothing. Phase 1 inventory is grep-driven pattern matching: the cheapest tier that fits. Phase 3/4 verification needs real judgment: floor each tag-family agent at tier 1 (sonnet), reserving the top tier for a family touching a risky surface (authn/authz/crypto/inject/llm). Run the closing integration pass at the strongest tier available — it's the one place seeing every finding at once.

Read the full file on GitHub · 448 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. today Changed · +78 lines cfd518198a51
  2. 4d ago First seen · 370 lines · 48 tokens per session scan B bca56e9caa67

Subscribe to this mod's changes

deadeye-vapt is a skill published in the GitHub repository deepaksinghcs14/deadeye-cc (5 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 6,397 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.

Related

Other skills, from other repositories

meta-tags-optimizer

Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…

nowork-studio/notfair-plugin · 91 tokens

google-ads-audit

Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…

nowork-studio/notfair-plugin · 114 tokens

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…

nowork-studio/notfair-plugin · 235 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens

security

Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.

oliver-kriska/claude-elixir-phoenix · 47 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens