wren

A marketplace listing for the Wren plugin, which bundles agent skills for Wren Engine. Wren Engine provides a semantic SQL layer and an MCP server for connecting to data sources.

In plain words
What is it for?
Use it to publish or identify the Wren plugin in a plugin marketplace.
Why use it?
It records the plugin’s ownership, description, version, and supported data-source keywords in a format the marketplace can use.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add Canner/wren-engine
agentmods
npx agentmods add plugins/canner/wren-engine/marketplace
Clone the repo
git clone --depth 1 https://github.com/Canner/wren-engine

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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 2d 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.

skills-archive/.claude-plugin/marketplace.json · 44 lines

What it actually says

{
  "name": "wren",
  "owner": {
    "name": "Canner",
    "email": "[email protected]"
  },
  "metadata": {
    "description": "Wren Engine skills — semantic SQL, MDL management, MCP server setup for 20+ data sources"
  },
  "plugins": [
    {
      "name": "wren",
      "source": ".",
      "description": "AI agent skills for Wren Engine — semantic SQL layer and MCP server for 20+ data sources.",
      "version": "1.0.0",
      "keywords": [
        "wren",
        "sql",
        "mdl",
        "mcp",
        "semantic-layer",
        "docker",
        "amazon-s3",
        "apache-spark",
        "apache-doris",
        "athena",
        "bigquery",
        "clickhouse",
        "databricks",
        "duckdb",
        "google-cloud-storage",
        "minio",
        "mysql",
        "oracle",
        "postgres",
        "redshift",
        "sql-server",
        "snowflake",
        "trino"
      ]
    }
  ]
}
Files

What ships with it

1 file beside marketplace.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.

Changes

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.

  1. 2d ago First seen · 44 lines scan A 827e2e6b83ec

Subscribe to this mod's changes

wren is a plugin published in the GitHub repository Canner/wren-engine (663 stars, last pushed 3mo 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.