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.
git 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/plugins/canner/wren-engine/skills-archive)<a href="https://agentmods.dev/plugins/canner/wren-engine/skills-archive"><img src="https://agentmods.dev/badge/plugins/canner/wren-engine/skills-archive/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/plugins/canner/wren-engine/skills-archive"><img src="https://agentmods.dev/badge/plugins/canner/wren-engine/skills-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wren 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 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.
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.
What it actually says
{
"name": "wren",
"description": "AI agent skills for Wren Engine — semantic SQL layer and MCP server for 20+ data sources.",
"version": "1.0.0",
"author": {
"name": "Canner",
"url": "https://www.getwren.ai/"
},
"homepage": "https://www.getwren.ai/",
"repository": "https://github.com/Canner/wren-engine",
"license": "Apache-2.0",
"keywords": [
"wren",
"sql",
"mdl",
"mcp",
"semantic-layer",
"data-source",
"docker",
"amazon-s3",
"apache-spark",
"apache-doris",
"athena",
"bigquery",
"clickhouse",
"databricks",
"duckdb",
"google-cloud-storage",
"minio",
"mysql",
"oracle",
"postgres",
"redshift",
"sql-server",
"snowflake",
"trino"
]
}
What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 749 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 39 lines scan A 6c19572dddbe
wren is a plugin published in the GitHub repository Canner/wren-engine (660 stars, last pushed 5mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
metaxy marketplace
Plugin marketplace listing 1 plugin: metaxy.
metaxy
Provides the /metaxy skill for guidance on feature definitions, versioning, and metadata stores, plus MCP tools for exploring feature graphs and querying metadata.
snowflake-dbt-migration
dbt migration skills for converting source database SQL to dbt models on Snowflake.
sparq
Usage skills for the sparq RDF triplestore + SPARQL 1.1/1.2 engine (Rust/CLI/HTTP/Python/WASM + reasoning, SHACL, full-text, vector, GeoSPARQL, RSP-QL, ZK query proofs).
agami-core
The trust layer between AI and your database, so an agent's answers are defensible. Every join, metric, and named filter is confidence-scored and either FK-derived or human-approved via a review dashboard. Every answer ships a SQL receipt showing what ran and which model version it used. Works across Postgres / MySQL…
data-engineering-skills
Data architecture, streaming pipelines, transformations, SQL optimization, and performance engineering.