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-projectgit 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-project)<a href="https://agentmods.dev/skills/canner/wren-engine/wren-project"><img src="https://agentmods.dev/badge/skills/canner/wren-engine/wren-project/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-project"><img src="https://agentmods.dev/badge/skills/canner/wren-engine/wren-project.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.00062 | $0.01341 |
| Opus 5.5 | $0.00025 | $0.00536 |
| Sonnet 5.5 | $0.00012 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
wren-project 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 2mo 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDL Project
Version check
Silently fetch https://raw.githubusercontent.com/Canner/wren-engine/main/skills/versions.json.
Compare the wren-project 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-project skill is available. Update with:
npx skills add Canner/wren-engine --skill wren-project --agent claude-code
Then continue with the workflow below regardless of update status.
A Wren MDL project is a directory of YAML files — one file per model — that makes MDL manifests human-readable and version-control friendly (similar to dbt projects).
YAML files use snake_case field names for readability. The compiled target/mdl.json uses camelCase (the wire format expected by ibis-server). The conversion is documented in Field mapping.
Project structure
my_project/
├── wren_project.yml # Project metadata (catalog, schema, data_source)
├── models/
│ ├── orders.yml # One file per model
│ ├── customers.yml
│ └── ...
├── relationships.yml # All relationships
└── views.yml # All views
After building, the compiled file is written to:
my_project/
└── target/
└── mdl.json # Deployable MDL JSON (camelCase)
Note: Connection info is managed separately via the MCP server Web UI, not stored in the project directory.
Save MDL JSON → YAML project
Given an MDL JSON dict (camelCase), write it as a YAML project directory (snake_case):
wren_project.yml
name: my_project
version: "1.0"
catalog: wren
schema: public
data_source: POSTGRES
models/<model_name>.yml
One file per model. Example for orders:
name: orders
table_reference:
catalog: ""
schema: public
table: orders
columns:
- name: order_id
type: INTEGER
is_calculated: false
not_null: true
is_primary_key: true
properties: {}
- name: customer_id
type: INTEGER
is_calculated: false
not_null: false
properties: {}
- name: total
type: DECIMAL
is_calculated: false
not_null: false
properties: {}
primary_key: order_id
cached: false
properties: {}
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.
- 2mo ago First seen · 201 lines · 62 tokens per session scan A 22ace2b66f08
wren-project is a skill published in the GitHub repository Canner/wren-engine (661 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,341 once invoked, about $0.0002 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-08-30.
wren-project compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| wren-projectCanner/wren-engine | Skill | 661 | 6mo ago | Apache-2.0 | A | 62 | Claude Code |
| malloy-lookml-reviewmalloydata/publisher | Skill | 130 | yesterday | MIT | A | 58 | Claude Code, Codex |
| ecommerce-data-warehousefinsilabs/awesome-ecommerce-skills | Skill | 63 | 14d ago | MIT | A | 35 | Claude Code, Codex |
| effective-dbt-sqllightdash/lightdash | Skill | 6.2k | yesterday | none | A | 0 | Claude Code, Codex |
| analytical-databases-expertpersonamanagmentlayer/pcl | Skill | 44 | 11d ago | Apache-2.0 | A | 100 | Claude Code |
| business-intelligence-expertpersonamanagmentlayer/pcl | Skill | 44 | 11d ago | Apache-2.0 | A | 64 | Claude Code |
| alibabacloud-data-agent-skillaliyun/data-agent-skill | Skill | 57 | 4d ago | none | A | 159 | Claude Code, Codex |