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-analyzegit 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-analyze)<a href="https://agentmods.dev/skills/malloydata/publisher/malloy-analyze"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-analyze/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-analyze"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-analyze.svg" alt="Reviewed on agentmods" width="80" 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.00113 | $0.02874 |
| Opus 5 | $0.00056 | $0.01437 |
| Sonnet 5 | $0.00023 | $0.00575 |
| Haiku 4.5 | $0.00011 | $0.00287 |
Grade A, and why
malloy-analyze 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 9d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analysis with Malloy
This skill covers two workflows:
- EDA exploration (Steps 1-6): iteratively query data, build hypotheses, validate findings
- View/dashboard building: create views, dashboards, notebooks from an existing model
Tool names are written bare here -
get_context,execute_query,search_malloy_docs. The exact prefixed name depends on the host surface; match each against the tools you actually have.
To formalize analysis into a polished semantic model, hand off to the modeling skill's "Starting from Analysis" workflow (skill:malloy-model).
Prerequisites
- The Malloy MCP tools must be configured (
get_context,execute_query,search_malloy_docs). If they are not available, STOP and ensure your host's MCP server is connected. - Call
search_malloy_docsliberally: it has powerful analysis patterns (window functions, cohorts, percent-of-total, nested drill-downs).
EDA WORKFLOW
ORIENT → PROFILE → HYPOTHESIZE → INVESTIGATE → VALIDATE → SYNTHESIZE
(user) (user) (user)
Adaptive Checkpoints
The 6-step structure is a framework, not a rigid script.
| Situation | Adaptation |
|---|---|
| User has a clear hypothesis ("what's driving churn?") | Skip HYPOTHESIZE, jump to INVESTIGATE on their question |
| Open-ended ("what's interesting?") | Follow all steps. PROFILE and HYPOTHESIZE are essential |
| User wants you to just go ("explore and show me") | Compress checkpoints, present findings at SYNTHESIZE |
Step 1: ORIENT: Understand the Data
- Ground yourself with
get_context. It returns the package's sources, views, and fields (with their docs), so this is where you learn what data exists. - Note the source names, the connection they sit on, and the key tables/fields they expose.
- Inspect the existing dimensions, measures, and views the model already defines, then query the data to confirm shape and values.
- Create a working analysis file (this grows throughout the session):
source: main_table is conn.table('schema.table') extend { primary_key: pk }
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.
- 9d ago First seen · 271 lines · 113 tokens per session scan A f2e9f5004863
malloy-analyze is a skill published in the GitHub repository malloydata/publisher (100 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 2,874 once invoked, about $0.0006 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.