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 mtarcure/claude-vibe-squad --skill known-advisory-backport-checkgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/known-advisory-backport-check)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/known-advisory-backport-check"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/known-advisory-backport-check/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/mtarcure/claude-vibe-squad/known-advisory-backport-check"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/known-advisory-backport-check.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.00070 | $0.00742 |
| Opus 5.5 | $0.00028 | $0.00297 |
| Sonnet 5.5 | $0.00014 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
known-advisory-backport-check 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 1mo 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 — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
known-advisory-backport-check
For any target that forks or pins a dependency (a forked cosmos/evm, an old cosmos-sdk/cometbft, a vendored library): known upstream vulnerabilities the target failed to patch are reachable, low-effort findings. Run this early — it's the cheapest high-value pass and it's what the 52-competitor crowd's osv-scan finds first.
Steps
- Enumerate pinned versions. Read
go.mod/Cargo.toml/package.jsonincludingreplace/=>directives (the replace wins — audit the ACTUAL resolved version, e.g.cosmos/evm => a bridge target/evm v1.0.0-rc2...). - Pull the advisory set.
osv-scanner --lockfile <lock>for the dep graph;gh api repos/<upstream>/security-advisoriesfor published GHSAs; the upstreamSECURITY.md/ release notes / advisory index (Hacken, Cosmos ASA, etc.). - For each Critical/High advisory: get
affected+first_patched_version(gh api /advisories/<GHSA>), compare to the pinned version. Behind the fix = candidate. - Reachability + config. Is the vulnerable module/function actually WIRED and reachable at no privilege in THIS target's config? (e.g. is
x/groupregistered + in EndBlock? is the ICS20 precompile activated? is the affected code path called?) A vuln in an unused code path doesn't pay. - Fork-diff for missing backports. If it's a fork of a release-candidate (
-rcN) or a frozen branch, the upstream may have shipped a security fix AFTER the fork point. Diff the fork vs upstream for the fix's presence — a code-pattern fix (e.g. a snapshot/journal wrap, a signer check) can be silently dropped in a merge even when the version looks recent. Confirm the guard is present at the pinned commit.
The scope/dedup reality (be honest — protect the rep)
- Known public CVEs are usually dedup-dead and often ruled "known / out-of-scope / third-party" —
osv-scanis the crowd's first move. Do NOT submit a stock reachable-CVE as-is expecting payment; it's a near-certain rejection + rep penalty. - What DOES convert: (a) a fix that is genuinely MISSING/INCOMPLETE in the fork at the pinned commit (novel to this deployment), or (b) a Push-/target-SPECIFIC elevation where custom code makes the generic bug reachable/impactful in a way the advisory didn't cover. Novelty + a runnable PoC is the bar.
- Either way: report the reachable-known ones to the project as free remediation (goodwill), and only SUBMIT the novel/incomplete-fix ones. Feed the decision to
impact-validator(G3 dedup, G4 scope). Related: [[chain-construct]].
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.
- 1mo ago First seen · 22 lines · 70 tokens per session scan A cc94ae60b7a1
known-advisory-backport-check is a skill published in the GitHub repository mtarcure/claude-vibe-squad (165 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 742 once invoked, about $0.0003 per session on Opus 5.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-09-19.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
skill-installer
Install, update, trust, or inspect Codewhale skills from GitHub or local skill folders. Use when the user asks for available skills or wants a community skill installed.