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 Canner/wren-engine --skill wren-onboardinggit clone --depth 1 https://github.com/Canner/wren-engineWrote 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/canner/wren-engine/wren-onboarding)<a href="https://agentmods.dev/skills/canner/wren-engine/wren-onboarding"><img src="https://agentmods.dev/badge/skills/canner/wren-engine/wren-onboarding/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/canner/wren-engine/wren-onboarding"><img src="https://agentmods.dev/badge/skills/canner/wren-engine/wren-onboarding.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.00098 | $0.02249 |
| Opus 5.5 | $0.00039 | $0.00900 |
| Sonnet 5.5 | $0.00020 | $0.00450 |
| Haiku 4.5 | $0.00010 | $0.00225 |
Grade B, and why
wren-onboarding scanned grade B with 1 finding 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
5. Add `.env` to `.gitignore` if the project is a git repo. Suggest `chmod 600 .env`. How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wren Onboarding — Agent Workflow
This skill walks the agent through onboarding — environment checks, project scaffolding, profile creation, MDL generation, and first query. Procedural details, per-datasource setup notes, and the troubleshooting playbook live in the docs, not here. The skill's job is to enforce the agent-side rules (one step per turn, never ask for credentials in chat) and to dispatch the agent to the right doc / sibling skill at each step.
Reference docs (the skill points to these — never duplicate their content):
docs/get_started/installation.md— CLI install + skill installdocs/get_started/connect.md— full connection procedure, per-datasource setup notes, complete troubleshooting playbookdocs/get_started/quickstart.md— bundledjaffle_shopdemo
Version check
Silently fetch https://raw.githubusercontent.com/Canner/wren-engine/main/skills/versions.json. Compare the wren-onboarding key with this skill's version (from the frontmatter above). If the remote version is newer, notify the user:
A newer version of the wren-onboarding skill is available. Update with:
npx skills add Canner/wren-engine --skill wren-onboarding
Continue regardless of update status.
Mode of operation — READ THIS FIRST
One step per round-trip. Each numbered step below is its own turn: explain briefly, ask only what the step needs, run the command(s), confirm, move on.
- ❌ Never collect information for future steps upfront. Do not ask for project name + database type + credentials in one message.
- ❌ Never ask for credentials in chat — not host, port, user, password, tokens, anything. Credentials always go through
.env. The user fills the file in their editor; the agent never sees the values. - ❌ Never query the database before MDL is built via the
wren-generate-mdlskill. - ❌ Never invent connection field names. Always run
wren docs connection-info <ds>to see the real fields — it's introspected from the live Pydantic schema, so it's always correct. - ✅ Wait for each command to finish, report its output in plain language, then move on.
- ✅ For any error, consult
connect.md#troubleshootingand surface the relevant section to the user — don't carry a copy of the playbook here.
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.
- 1mo ago First seen · 168 lines · 98 tokens per session scan B e1290309df3e
wren-onboarding is a skill published in the GitHub repository Canner/wren-engine (660 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 2,249 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). 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…
malloy-model
Build Malloy semantic models with base source and joined source files. Use when creating or modifying .malloy files, user asks to "create a malloy model", "add dimensions", "add measures", "create a source", or any Malloy model authoring task.
eval-import
Turn a list of questions into an eval set, whatever shape it arrived in: a JSONL a customer sent, a CSV, a spreadsheet export, a markdown doc, an email thread, or a pull from production logs. Classify each item by what came WITH the question (a query, a number, prose criteria, or nothing), write cases.jsonl and…
malloy-model-as-you-go
After answering a data question, write down what the answer assumed so the next reader can trust the number. A field with a #(doc) in the model when you can edit it, an extend in the notebook when you can only author reports, or a stated assumption plus a Malloy snippet when you can only chat. Use after every answered…
malloy-define
Propose scope, a source plan and field definitions for a Malloy model. Which tables and questions, which sources at what grain, then renames, dimensions and measures, each backed by querying data.