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/malloydata/publisher/malloynpx skills add malloydata/publisher --skill malloygit 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)<a href="https://agentmods.dev/skills/malloydata/publisher/malloy"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy.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.00046 | $0.01479 |
| Opus 5 | $0.00023 | $0.00740 |
| Sonnet 5 | $0.00009 | $0.00296 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
malloy 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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Malloy Skills Index
First-Time Setup
No .malloy files in workspace? Say "model my data" and the agent will orchestrate the full modeling workflow automatically. Make sure the Malloy Publisher MCP tools are configured first.
Skill Reference
Every skill in this deployment, by what it is for. Start at a driver; it routes to the rest.
This table is a catalogue of what exists, not of what is loaded. A host that installs one group takes that group's skills alone: analysis, modeling, or eval. A row naming a skill from a group you did not install says that the skill exists. It is not an instruction to load it, and it is written as a plain name rather than a skill: reference to say so.
Start here
| Skill | Use when... |
|---|---|
skill:malloy-getting-started |
First contact with a Publisher: confirming the tools, finding what data exists, running a first grounded query |
skill:malloy-modeling |
Building a semantic model from scratch (the modeling workflow driver) |
skill:malloy-analysis |
Answering a data question or exploring data (the analysis workflow driver) |
Modeling phases (driven by skill:malloy-modeling)
| Skill | Use when... |
|---|---|
skill:malloy-discover |
Silent data discovery: tables, schemas, distributions, prior art |
skill:malloy-scope |
Presenting findings and proposing an analytical focus |
skill:malloy-define |
Proposing the source plan and field definitions |
skill:malloy-model |
Writing base and joined source .malloy files, review, curate (includes normalized schema support) |
skill:malloy-document |
Adding #(doc) tags for discoverability |
skill:malloy-lookml-review |
Prior-art adapter for LookML (field extraction, derived tables, visibility, docs) |
Analysis and presentation
| Skill | Use when... |
|---|---|
skill:malloy-model-as-you-go |
After answering a question, writing down what it assumed: a #(doc)'d field in the model, an extend in the notebook, or a stated assumption plus snippet, depending on what the session can write |
skill:malloy-analyze |
Open-ended exploration with no intent to keep anything: profiling, hypotheses, views |
skill:malloy-charts |
Chart selection and renderer reference for Malloy visualizations |
skill:malloy-notebooks |
Building Malloy notebooks (.malloynb) |
skill:malloy-analysis-report |
Combining validated queries into a notebook report or dashboard |
skill:malloy-analysis-pitfalls |
Checking a query and its results before presenting an answer |
malloy-notebook-chat |
The chat is bound to a notebook or saved report; answer from its cells. Ships in analysis. |
skill:malloy-phrase-detection |
Turning a plain-English question into search targets for the context tool |
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.
- 2d ago Changed · +11 lines 8ab7d4ba24d5
- 6d ago First seen · 91 lines · 46 tokens per session scan A 838a3934346d
malloy is a skill published in the GitHub repository malloydata/publisher (100 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,479 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
debug-local
Debug the Lightdash app using PM2 logs, Maple traces, and browser automation. Use when investigating issues, tracking down bugs, understanding request flow, or correlating frontend actions with backend behavior.
frontend-style-guide
Apply the Lightdash frontend style guide and design principles when working on React components or styling frontend code. Use when editing TSX files, building or reviewing UI, fixing styling issues, or when the user mentions Mantine, design, styling, or CSS modules.
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…
lightdash-agent-slack-messaging
Use this skill when writing, designing, or generating Slack messages for Lightdash's in-app analytics agent. Triggers when someone asks to create agent update messages, Slack digests, agent notifications, weekly summaries, daily summaries, or any Slack copy for the Lightdash project agent. Also use when asked to vary…
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…
breakup-pr
Break up a large PR into vertical feature slices delivered incrementally via Graphite stacked PRs. All verticals share a single feature flag so the entire feature ships atomically. Use when: splitting a large PR, breaking up a diff, vertical slicing, incremental delivery, phased rollout, or when a PR is too large to…