Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tinoimammp/vantage-security-agent/plugin install vantageWrote 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/commands/tinoimammp/vantage-security-agent/scan-web)<a href="https://agentmods.dev/commands/tinoimammp/vantage-security-agent/scan-web"><img src="https://agentmods.dev/badge/commands/tinoimammp/vantage-security-agent/scan-web.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.1 | $0.00018 | $0.00602 |
| Opus 5 | $0.00009 | $0.00301 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
scan-web 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 8d 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.
What it actually says
Run the complete web vantage pipeline against $ARGUMENTS (default:
current working directory), phases 01 through 06, honoring the gates in
${CLAUDE_PLUGIN_ROOT}/workflow/orchestration.md.
Read ${CLAUDE_PLUGIN_ROOT}/START-HERE.md and
${CLAUDE_PLUGIN_ROOT}/workflow/orchestration.md first if you have not
already this session.
- If
./.vantage/artifacts/recon/scope.jsondoesn't exist, copy the plugin asset${CLAUDE_PLUGIN_ROOT}/artifacts/recon/scope.json.template→./.vantage/artifacts/recon/scope.json, filling in placeholders with the current system timestamp and repository path. Never block to ask the user. - Set/confirm
platform: "web"in thatscope.json— this command always runs the web pipeline regardless of what's already there (if it says"mobile", overwrite it to"web"for this run and note that you did so). - For each phase, in order, check the phase's gate is satisfied (per
${CLAUDE_PLUGIN_ROOT}/workflow/orchestration.md) — if not, stop and report why — then dispatch via Task:- 01 Recon →
recon-agent - 02 Mapping →
mapper-agent - 03 Testing → dispatch all 10 as parallel Task calls in the same
turn, each writing its own
raw-findings.<agent-name>.json:auth-agent,authorization-agent,api-agent,sqli-agent,xss-agent,upload-agent,business-logic-agent,injection-agent,dependency-agent,secrets-agent - 04 Validation →
validator-agent(merges allraw-findings.*.jsonfirst) - 05 PoC →
poc-agent(only if ≥1validated:truefinding) - 06 Reporting →
report-agent
- 01 Recon →
- Append each phase's result to
./.vantage/artifacts/run-log.md.
Stop and summarize if a phase produces zero actionable output (see Failure &
Empty Handling in ${CLAUDE_PLUGIN_ROOT}/workflow/orchestration.md) — do
not fabricate findings.
When done, report the final artifact path —
./.vantage/artifacts/reports/report.md — and remind the user that
/vantage:fix-issue <id> or /vantage:fix can apply code-level fixes for
the validated findings.
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.
- 8d ago First seen · 45 lines · 18 tokens per session scan A 0e8ad951d7bb
scan-web is a command published in the GitHub repository tinoimammp/vantage-security-agent (4 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 602 once invoked, about $0.0001 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 commands, from other repositories
review-cheatsheet-pr
Aggressively review an OWASP cheat sheet PR across security, practicality, links/sources, duplication, and language; produce a single MERGE/REQUESTCHANGES/CLOSE verdict.
scope
Prepare a focused analysis scope for large codebases or monorepos using repomix. Creates a digestible snapshot of the target code for subsequent security analysis.
threats
Combines application understanding with systematic threat identification. First understands the application, then identifies what could go wrong.
propagate
When you find one vulnerability, search for the same pattern everywhere else. Developers often make the same mistake repeatedly.
mobile-audit
End-to-end mobile audit driver for Android targets. Most Android bug-bounty work involves a decompiled APK that's been split into two directories.
trace
Trace attacker-controlled input to a sink and document whether it is a verified vulnerability, a hotspot that still needs proof, or a false positive.