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/waybarrios/opencode-power-pack/vuln-reportnpx skills add waybarrios/opencode-power-pack --skill vuln-reportgit clone --depth 1 https://github.com/waybarrios/opencode-power-packWrote 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/waybarrios/opencode-power-pack/vuln-report)<a href="https://agentmods.dev/skills/waybarrios/opencode-power-pack/vuln-report"><img src="https://agentmods.dev/badge/skills/waybarrios/opencode-power-pack/vuln-report.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.00044 | $0.01560 |
| Opus 5 | $0.00022 | $0.00780 |
| Sonnet 5 | $0.00009 | $0.00312 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
vuln-report 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vuln-report — 91% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Report
Overview
Draft one disclosure-ready report for one confirmed bug. Keep the report evidence-driven, concrete, and concise. Prefer the section order and phrasing rules in references/report-template.md.
Workflow
- Confirm the report is about one bug only.
- Extract the minimum facts needed to prove the issue:
- vulnerable component or behavior
- attacker-controlled input or missing validation
- preconditions and trust boundary
- exploit result
- practical impact
- strongest reproduction path
- decisive source locations and any relevant fix commit
- Separate demonstrated facts from inference. State assumptions explicitly.
- Draft the report using the required section order from references/report-template.md.
- Always embed at least one fenced code snippet from the decisive code path, and explain what each snippet proves.
- Always convert repository file references and patch references into GitHub markdown links, and prefer embedding those links directly into the surrounding explanation instead of listing them separately.
- Add only the optional sections that materially improve accuracy or triage value.
- Save the final report as
report.mdinside a folder named with the bug's severity identifier (C1,H1,M1, etc.) followed by a lowercase hyphenated slug derived from the final report title. UseCfor Critical,Hfor High,Mfor Medium, sequentially numbered if there are multiple bugs of the same severity. Example:C1-cross-site-websocket-hijacking-re-enabled-by-allow-websocket/report.md. Also, ensure the bug report title and internal references use this ID (e.g., '[C1] Cross-Site WebSocket Hijacking'). Do not write reports for Low severity findings — document them in the summary table only. - Remove filler, hedging, and unproven claims before finalizing.
Required Sections
Always include these sections in this order:
SummaryDetailsRoot CauseProof of Concept (PoC)Impact
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 117 lines · 44 tokens per session scan A cba9f739f3eb
vuln-report is a skill published in the GitHub repository waybarrios/opencode-power-pack (490 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 1,560 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-30.
Other skills, from other repositories
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
code-understand
Build a ranked, citation-backed focus map of a codebase — the files and symbols an architecture actually hangs on — using CodeGraph when available and a dependency-free builtin (regex AST extraction + rg cross-file references) otherwise. Use this any time you (the coding agent) need to orient in an unfamiliar or large…
cozempic-doctor
Run health checks on Claude Code configuration and sessions. Use when troubleshooting Claude Code issues. (cozempic — does not shadow Claude Code's built-in /doctor).
diagnose
Analyze Claude Code session bloat — shows token count, context usage %, and bloat breakdown. Use when the user asks about session size, context usage, or when you notice the context window is getting full.
ci-triage
Diagnose and fix red CI on zaxy — fetch the right logs, reproduce locally despite the known local quirks (testdoctor hang, benchmark tables), do coverage-ratchet math correctly, and apply the test-vs-source intent rule. Use when CI is red, a check fails on a PR, "make master green", or coverage ratchet fails.
lain
Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…