Borrowing it
Nothing to install: this file belongs to malloydata/publisher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/malloydata/publisher/main/.claude/skills/fix-scan-finding/SKILL.mdgit clone --depth 1 https://github.com/malloydata/publisherWrote 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/malloydata/publisher/fix-scan-finding)<a href="https://agentmods.dev/skills/malloydata/publisher/fix-scan-finding"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/fix-scan-finding/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/malloydata/publisher/fix-scan-finding"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/fix-scan-finding.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.00157 | $0.05044 |
| Opus 5.5 | $0.00063 | $0.02018 |
| Sonnet 5.5 | $0.00031 | $0.01009 |
| Haiku 4.5 | $0.00016 | $0.00504 |
Grade A, and why
fix-scan-finding 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 20d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixing a security-scan finding
Audience: a contributor or agent working a CVE, Trivy, or code-scan finding in this repository --
fixing a red CRITICAL gate, or verifying a finding on a gate that is already green. No prior Trivy
expertise assumed.
Prerequisites: trivy on PATH (brew install trivy, or see the Trivy install docs), bun at
the version in the root package.json engines, and Docker with buildx for image findings. No
cloud credentials are needed -- everything here is local and read-only against public registries.
What CI scans
| Workflow | Job | Reads |
|---|---|---|
.github/workflows/security-scan.yml |
Trivy filesystem scan (vulnerabilities) |
every lockfile in the tree |
.github/workflows/security-scan.yml |
Trivy config scan (Dockerfiles) |
the Dockerfiles only: Trivy's misconfiguration scanner does not read GitHub Actions workflows |
.github/workflows/security-scan.yml |
Trivy secret scan |
the working tree |
.github/workflows/image-scan.yml |
Trivy image scan (built from source, <platform>) |
the Dockerfile built from the PR, once per platform the release publishes (linux/amd64, linux/arm64) |
.github/workflows/image-scan.yml |
Trivy image scan (published latest, <platform>) |
ms2data/malloy-publisher:latest on both platforms, weekly schedule and dispatch |
Each job uploads its full SARIF to Code Scanning, then runs a second scan scoped to CRITICAL with
exit-code: 1. CRITICAL fails the job, and the secret gate fails on HIGH as well: a committed
credential is an incident whatever its rating. GitHub's own "Trivy" Code Scanning check on a pull
request is set, in the repository's code scanning settings, to fail only on critical alerts. It
treats every alert in a file the PR touches as new, and a lockfile is one file, so at a high
threshold every dependency PR went red on alerts already open on main. If that check goes red on
high again, the setting was changed; that is the fix, not a lockfile edit. GitHub rates an alert
by the SARIF's CVSS score, not Trivy's label, so the two can disagree: a Trivy MEDIUM can show as
high, and a Trivy HIGH with CVSS 9.0 or more is critical to GitHub and still fails the check. HIGHs
still land in Code Scanning, and one with a reachable fix is still worth fixing. Every job reads
the same .trivyignore.yaml. On a pull request from a fork the SARIF upload is skipped (the token
is read-only), but the gate still runs, so read the job log there.
What ships with it
2 files 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.
- 20d ago Changed c5531d3a3c79
- 21d ago Changed · +9 lines 0083c346cdc3
- 22d ago First seen · 292 lines · 157 tokens per session scan A 69c4f1ffdb5f
fix-scan-finding is a skill published in the GitHub repository malloydata/publisher (118 stars, last pushed today), licensed MIT. It adds 157 tokens to every session and 5,044 once invoked, about $0.0006 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-30.
Other skills, from other repositories
reimagine-it-extract
Emit the content signals reimagine-it reads from an HTML file — title, anchors, proper nouns, dates, numbers, emails, links, source hex colors, and the derived palette — as JSON without generating a redesign. Use when the user says /reimagine-it extract, "what does the engine see in this page", "extract the palette"…
reusable-visualization
Build ONE reusable chart visualization component that receives its data and its settings from the host application instead of fetching them, and declares the fields and config options the host exposes to viewers. Use this whenever a single chart component is reused across many different queries rather than built for…
repository-writeback
Use when changing the dbt project through a pull request (editDbtProject) or managing those pull requests, offering to fix or extend the semantic layer, or following up a merged pull request.
developing-in-lightdash
Use when reading, creating, and editing Lightdash dashboards and charts as JSON, including dashboard layout and chart-type-specific configuration.
sdk-features
Map Lightdash SDK capabilities to their host-UI names and the app-code wiring each needs. Use when the user asks about a feature by name (Inspect data, drill-down, exports, shareable URLs), when offering newly available features after a template upgrade, or when wiring a host-facing capability into the app.
upgrade-preflight
Checks whether a self-hosted Lightdash upgrade is safe to run, and reads the tooling's answer without over-reading it. Use when upgrading a self-hosted instance, planning a maintenance window, answering "is this upgrade safe", or recovering a failed, hung, parked or lock-stuck migration — covers lightdash…