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/canner/wren-engine/wren-usagenpx skills add Canner/wren-engine --skill wren-usagegit clone --depth 1 https://github.com/Canner/wren-engineWhat 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 | $0.00126 | $0.01581 |
| Opus 5 | $0.00063 | $0.00790 |
| Sonnet 5 | $0.00025 | $0.00316 |
| Haiku 4.5 | $0.00013 | $0.00158 |
Grade A, and why
wren-usage 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 3d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wren Engine — Usage Guide
Version check
Silently fetch https://raw.githubusercontent.com/Canner/wren-engine/main/skills/versions.json.
Compare the wren-usage key with this skill's version (from the frontmatter above).
If the remote version is newer, notify the user before proceeding:
A newer version of the wren-usage skill is available. Update with:
npx skills add Canner/wren-engine --skill wren-usage --agent claude-code
Then continue with the workflow below regardless of update status.
This skill is your day-to-day reference for working with Wren Engine. It delegates to focused sub-skills for each task.
Step 0 — Install dependent skills (first time only)
Check whether the required skills are already installed in ~/.claude/skills/. If any are missing, tell the user to run:
# Option A — npx skills (works with Claude Code, Cursor, and 30+ agents)
npx skills add Canner/wren-engine --skill '*' --agent claude-code
# Option B — Clawhub (if installed via clawhub)
clawhub install wren-usage
This installs wren-usage and its dependent skills (wren-connection-info, wren-generate-mdl, wren-project, wren-sql, wren-mcp-setup, wren-http-api) into ~/.claude/skills/.
After installation, the user must start a new session for the new skills to be loaded.
If the user only wants the MCP server set up (no Docker yet), use
/wren-quickstartfor a guided end-to-end walkthrough instead.
What do you want to do?
Identify the user's intent and delegate to the appropriate skill:
| Task | Skill |
|---|---|
| Write or debug a SQL query | @wren-sql |
| Connect to a new database / change credentials | @wren-connection-info |
| Generate MDL from an existing database | @wren-generate-mdl |
| Save MDL to YAML files (version control) | @wren-project |
Load a saved YAML project / rebuild target/mdl.json |
@wren-project |
| Add a new model or column to the MDL | @wren-project |
| Start, reset, or reconfigure the MCP server | @wren-mcp-setup |
| Call Wren tools via HTTP JSON-RPC (no MCP SDK) | @wren-http-api |
| First-time setup from scratch | @wren-quickstart |
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.
- 3d ago First seen · 169 lines · 126 tokens per session scan A 6117d6c9e798
wren-usage is a skill published in the GitHub repository Canner/wren-engine (663 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 126 tokens to every session and 1,581 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
malloy-gotchas-modeling
Common Malloy modeling mistakes and how to avoid them. Read BEFORE writing source definitions, dimensions, measures, or joins. Covers reserved words, NULL checks, date functions, type casts, field management (extend except/accept/rename vs include public/internal/private), and query-based source gotchas.
malloy-materialization
Add and debug Malloy Persistence materializations in a package - persist an expensive source so queries read a pre-built table. Read this whenever the user wants to materialize a source, add a persist annotation, speed up a slow source, or asks why a persist source isn't building.
malloy-analyze
Open-ended exploration with no specific question to answer, and building views/dashboards/notebooks on an existing model. Use when the user asks "what's interesting?", "explore this data", "find insights", "look for patterns", "build a dashboard", or "create views". Not for a specific data question - answering one is…
malloy-html-data-app-runtime
Write the JavaScript that drives an in-package HTML data app, calling Publisher.query, building queries from filter state, and handling results and errors. Read before writing the page's data code.
malloy-document
Add documentation with #(doc) tags to Malloy models so fields and sources are described in plain language. Use when user asks to "add documentation", "add doc tags", "document the model", or wants fields and sources described for natural-language search and discovery. For declaring parameterizable filters with…
malloy-materialization-tuning
Optimize a package's Malloy Persistence materializations for cost and performance using the malloy-pub CLI and the materialization history. Recommend what to persist, what to stop persisting, and how to schedule/scope it. Use when the user asks to make a package cheaper or faster, tune persistence, decide what to…