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 skills add allsmog/vuln-scout --skill package-evidencegit clone --depth 1 https://github.com/allsmog/vuln-scoutWrote 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/allsmog/vuln-scout/package-evidence)<a href="https://agentmods.dev/skills/allsmog/vuln-scout/package-evidence"><img src="https://agentmods.dev/badge/skills/allsmog/vuln-scout/package-evidence/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.
<a href="https://agentmods.dev/skills/allsmog/vuln-scout/package-evidence"><img src="https://agentmods.dev/badge/skills/allsmog/vuln-scout/package-evidence.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00209 |
| Opus 5 | $0.00010 | $0.00105 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
package-evidence 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 12d 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
Package Evidence
Use this task skill when the user asks to package evidence, export a bundle, create a deliverable, or share findings.
Workflow
- Confirm
.claude/findings.jsonexists and validates. - Run
/vuln-scout:report --format sarif. - Run
/vuln-scout:report --format html. - Run
/vuln-scout:report --format bundle --output evidence-bundle. - Confirm the bundle contains
findings.json,findings.sarif,vex.json,attestation.json,report.html, andREADME.md.
Produces
evidence-bundle/
When NOT To Trigger
Do not trigger for starting a new audit, investigating a single finding, compliance mapping, report formatting preferences, or questions about evidence theory without a deliverable request.
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.
- 12d ago First seen · 25 lines · 19 tokens per session scan A 9a711f52ecf5
package-evidence is a skill published in the GitHub repository allsmog/vuln-scout (24 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 209 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-30.
Other skills, from other repositories
gather
A document-collection guide for Japanese tax filing that lists the documents needed for the filing type and explains where and how to obtain them.
submit
A final tax-return review and submission workflow for Japan, covering checks before filing and submission by e-Tax, mail, or in person.
sast-config
Reviews and tunes SAST tool configurations against OWASP ASVS 4.0.3 and CWE Top 25. Auto-invoked when reviewing Semgrep rules, CodeQL queries, SAST CI integration, or false positive triage workflows. Produces a SAST maturity assessment covering rule authoring, severity tuning, custom rule development, and CI…
pks
Generate PKS (Cooperation Agreement / Perjanjian Kerja Sama) DOCX by filling the official UPI template's partner placeholders.
especialista-em-pop
Especialista em Procedimento Operacional Padrão (POP). Use para criar POPs claros e auditáveis: estrutura, passos, responsáveis, controle de versão e conformidade. Palavras-chave: POP, SOP, procedimento, padronização, passo a passo, controle de versão, auditoria.
sast-semgrep
Static application security testing (SAST) using Semgrep for vulnerability detection, security code review, and secure coding guidance with OWASP and CWE framework mapping. Use when: (1) Scanning code for security vulnerabilities across multiple languages, (2) Performing security code reviews with pattern-based…