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-scopegit 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-scope)<a href="https://agentmods.dev/skills/malloydata/publisher/malloy-scope"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-scope.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.00040 | $0.01466 |
| Opus 5 | $0.00020 | $0.00733 |
| Sonnet 5 | $0.00008 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
malloy-scope 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 7d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propose Analytical Scope
When: After you have inspected the model and its underlying data. You have read the package's sources and fields and looked at the data distributions.
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.
Goal: Present what you found and recommend an analytical focus. The user selects a direction.
Ground yourself first with get_context: it returns the package's sources, views, and fields, so it tells you what data exists, how it relates, and what is already modeled. Query the data with execute_query to get row counts and spot data-quality issues. Record the proposal and the user's decision in your modeling workflow's modeling-notes.md.
Scope is "which questions", not just "which tables". A single A/B/C question about table inclusion is step 3's architecture question wearing step 2's clothes. The scope proposal must establish what the model is for: a model aimed at recommendation looks different from one aimed at catalog analysis over the same tables.
What to Present
1. Table Summary
Present a table of the discovered tables with key metadata:
| Table | Rows | Columns | Role | Key Relationships |
|---|---|---|---|---|
| orders | 1.2M | 24 | Fact | FK: customer_id → customers, product_id → products |
| customers | 50K | 15 | Dimension | PK: customer_id |
| products | 2K | 12 | Dimension | PK: product_id |
| order_items | 3.5M | 8 | Bridge | FK: order_id → orders, product_id → products |
| audit_log | 10M | 6 | Operational | No joins to business tables |
Classify each table by role:
- Fact: the events or transactions you measure (orders, sessions, payments).
- Dimension: the entities you slice by (customers, products, regions).
- Bridge: many-to-many linking tables (order_items, tags).
- Operational: ETL, staging, or audit tables that aren't analytical.
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.
- 7d ago First seen · 109 lines · 40 tokens per session scan A 34b711374d60
malloy-scope is a skill published in the GitHub repository malloydata/publisher (100 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,466 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
effective-dbt-sql
Use when writing or modifying dbt model SQL — deciding whether to add a subquery or reuse an existing dimension/metric, structuring a query, joining models, or refactoring a metric's SQL. Encodes SQL semantic-correctness rules: reuse existing fields, prefer CTEs over correlated subqueries, and make joins and column…
alibabacloud-data-agent-mcp-skill
Alibaba Cloud Data Agent MCP skill (alibabacloud-data-agent-mcp-skill, data-agent MCP) for enterprise database/file analysis. Use when the user asks (in any language, including Chinese) to query/analyze DMS-managed databases, run SQL/data analysis, start quick-query (lite) or deep-analysis (pro/ultra) sessions…
wren-usage
Wren Engine — semantic SQL engine for AI agents. Query 22+ data sources (PostgreSQL, BigQuery, Snowflake, MySQL, ClickHouse, etc.) through a modeling layer (MDL). This skill is the main entry point: it guides setup, delegates to focused sub-skills for SQL authoring, MDL generation, project management, and MCP server…
wren-onboarding
Onboard a user to Wren Engine end-to-end. Walks through environment checks, project scaffolding, connection configuration via .env, and first query. Use when: user wants to install Wren Engine, set up a new data source connection, or bootstrap a new project from scratch. Triggers: '/wren-onboarding', 'install wren'…
arrowspace
Spectral vector search using graph Laplacian eigenstructure. Use when cosine/L2 similarity misses latent structure in your embeddings.
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.