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 malloydata/publisher --skill malloy-reportsgit 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/malloy-reports)<a href="https://agentmods.dev/skills/malloydata/publisher/malloy-reports"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-reports/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/malloy-reports"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-reports.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.00123 | $0.05968 |
| Opus 5.5 | $0.00049 | $0.02387 |
| Sonnet 5.5 | $0.00025 | $0.01194 |
| Haiku 4.5 | $0.00012 | $0.00597 |
Grade A, and why
malloy-reports 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 today.
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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publisher Reports
A
.malloyfile with an## artifact { layout=… tiles=[…] }tag is a report. It imports the model, names the views to show, binds the filtering on those views, and says how to lay them out. Publisher discovers it at package load, renders the filter controls from the givens its tiles reference, offers# drillclick-through, and serves it at/<env>/<pkg>/<path>, its package path without.malloy. No code, no build step.
What other tools call a dashboard and a notebook are both reports here. The layout is the only difference:
layout=grid: tiles across a grid behind one filter row, scanned at a glance (a dashboard). Readreference/grid.mdbefore you lay one out.layout=linear: tiles and prose top to bottom, read in order (a notebook, a data story). Readreference/linear.mdbefore you write one.
Everything else (filters, text tiles, drill, the builder, the lint, the write path) is the same for both, and switching layout later is a one-property edit.
Where the file goes
- Write a new report at the package root, as
<slug>.malloy, unless the author asks for another location. No directory is required, and none is a convention: a report can live anywhere in the package exceptpublic/, and the rootindex.malloyis never a report. Do not create adashboards/ornotebooks/directory for it. - Always write
layout=gridorlayout=linearin the tag. A tag without one is read by a fallback rule, and a linear report that lists tiles withoutlayout=linearis read as a grid.kind=is no longer read: a tag that sets it makes no report (report-kind-removed), so replace it withlayout=. - The package path is the report's identity.
sales/q3.malloyis the reportsales/q3: its URL, itsGET …/reports/{path}address, and its# drilltarget. Two reports may share a basename in different directories. - Imports are relative to the report's own location. At the root:
import { order_items } from "storefront.malloy". In a subdirectory:"../storefront.malloy". - An untagged
.malloyfile is an ordinary model, wherever it lives. Shared definitions several reports import go in one.
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.
- today Changed 39d5a1c94974
- yesterday Changed · +65 lines 175fc172c306
- 3d ago Changed · -2 lines 16aec8117048
- 4d ago First seen · 240 lines · 123 tokens per session scan A 8b69b10b0981
malloy-reports is a skill published in the GitHub repository malloydata/publisher (118 stars, last pushed today), licensed MIT. It adds 123 tokens to every session and 5,968 once invoked, about $0.0005 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-10-12.
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…
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…
developing-data-apps-locally
Use when editing a locally created or downloaded Lightdash data app — how local editing, building, and uploading work, and what is read-only.