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-modelinggit 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-modeling)<a href="https://agentmods.dev/skills/malloydata/publisher/malloy-modeling"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-modeling.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.04181 |
| Opus 5 | $0.00016 | $0.02090 |
| Sonnet 5 | $0.00007 | $0.00836 |
| Haiku 4.5 | $0.00003 | $0.00418 |
Grade A, and why
malloy-modeling 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 8d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP - READ BEFORE WRITING ANY MALLOY CODE
AI AGENTS: You MUST review this file before writing Malloy code. Cross-skill references below use logical
skill:names; load the referenced skill before acting. Before writing code, also read the gotcha skills:skill:malloy-gotchas-modeling,skill:malloy-gotchas-queries, andskill:malloy-gotchas-rendering.
Pre-Flight Checklist
- Discover first: ground yourself before writing ANY code, with the tool that matches what you are modelling.
- Modelling data already in a package:
malloy_getContextreturns that package's sources, views, and fields (with their docs). - Modelling a database with no package yet:
malloy_getContexthas nothing to return, so usemalloy_searchDatabaseSchemainstead. It walks the connection's schemas and tables, ranks them against a plain-English description, and gives you each table's columns plus thesource:line to start from. Take those names verbatim into step 5. Never guess field names either way.
- Modelling data already in a package:
- Search docs proactively: call
malloy_searchDocsBEFORE writing unfamiliar patterns (window functions, query-based sources, pipelines). Don't guess. Malloy syntax is specific and SQL intuition is often wrong. - Use
skill:malloy-patternsto discover available doc topics (YoY, cohorts, rendering, window functions). - Check diagnostics after writing: fix the FIRST error first, errors cascade.
- Read the gotcha skills:
skill:malloy-gotchas-modeling,skill:malloy-gotchas-queries, andskill:malloy-gotchas-renderingprevent the most common mistakes.
Quick syntax reminders:
- Backtick reserved words:
`Date`,`Hour`,`Timestamp`,`Type`,`number`,`source` - Use
having:for aggregate filters: notwhere:on measures - Alias joined fields in
group_byif using them inorder_by count()counts rows;count(x)counts distinct values ofx:count(distinct x)is deprecated, writecount(x)- One tag per line:
# label="Revenue"and# currencyon separate lines - No fixed scale on measures: use
# currencynot# currency=usd0m - Cast strings for aggregates:
avg(score::number)notavg(score) - Boolean columns: use
= truenot= 'true'(no quotes!) - Read data files in place:
.csv,.parquet,.json,.ndjson, and.xlsxall work as-is throughduckdb.table('data/file.ext'). Never convert a file to another format first, and never read one with python or jq to "have a look" first: query it. For.xlsx, check the row count before trusting it: a workbook with a title row or a blank spacer reads short and reports no error. (Per-format quirks:skill:malloy-gotchas-modeling)
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.
- 8d ago First seen · 218 lines · 33 tokens per session scan A 89636f023b25
malloy-modeling is a skill published in the GitHub repository malloydata/publisher (100 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 4,181 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
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…
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…
developing-in-lightdash
Use when reading, creating, and editing Lightdash dashboards and charts as JSON, including dashboard layout and chart-type-specific configuration.
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.