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-source-unreachablegit 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-source-unreachable)<a href="https://agentmods.dev/skills/malloydata/publisher/malloy-source-unreachable"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-source-unreachable/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-source-unreachable"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/malloy-source-unreachable.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.00086 | $0.02019 |
| Opus 5.5 | $0.00034 | $0.00808 |
| Sonnet 5.5 | $0.00017 | $0.00404 |
| Haiku 4.5 | $0.00009 | $0.00202 |
Grade A, and why
malloy-source-unreachable 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 yesterday.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A source you cannot reach
Tool names are written bare here -
get_context,execute_query,get_status,compile_model. The exact prefixed name depends on the host surface; match each against the tools you actually have.
Most packages publish a curated surface, so a source being absent or refused is usually the package working as its author intended, not a fault. Read the refusal before working around it, because the three things that can refuse you need three different responses and they are told apart by the status code.
The three answers
| what you got | what it means | what to do |
|---|---|---|
| 404 that says "not on this package's published surface" | the name is real and the package does not publish it. It is curation, not a typo | follow the fix the message names (usually: name it in the export { ... } of index.malloy and address the query there), or query what IS published |
| 404, plain "No queryable source", "No queryable model" or "Query target is not queryable" | the name does not exist, or it is hidden in a model that carries an #(authorize) or #(access_filter) gate. In a gated model the two are deliberately indistinguishable, so a refusal cannot be used to probe for hidden names |
check the name against get_context, then query something on the surface or ask the package's author to publish it |
| 403, "Access denied" | the source exists and is on the surface, but an #(authorize) gate did not admit you |
supply the givens the gate reads, or accept that this caller may not read it |
| 200 with zero rows | you were admitted, and an #(access_filter) narrowed the rows to none of them |
this is a real answer. Report it as "no matching rows", never as an error |
A 403 names a source, so it tells you the source exists. A plain 404 tells you nothing at all. That asymmetry is deliberate: a source that is both hidden AND gated answers a plain 404, so you can never use a 403, or the wording of a 404, to discover that a hidden gated name is real.
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.
- yesterday Changed · -1 lines 0cba78bb46cd
- 4d ago Changed f1ee501db002
- 9d ago Changed 849a7e201f01
- 15d ago Changed · +2 lines 8f2647804afd
- 20d ago Changed · +10 lines e0fea092b94c
- 21d ago Changed · +1 lines 9a6453434b0a
- 22d ago First seen · 71 lines · 86 tokens per session scan A 2ad1f902c180
malloy-source-unreachable is a skill published in the GitHub repository malloydata/publisher (118 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 2,019 once invoked, about $0.0003 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-09-24.
Other skills, from other repositories
mcp-artifact-integration
Integrate Lightdash MCP query results into Claude-created HTML or React artifacts. Covers host bridges, response envelopes, polling, errors, CSV fallback and chart data. Not needed for ordinary chat or Lightdash's built-in chart app.
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.