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/Data-Wise/claude-pluginsWrote 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/data-wise/claude-plugins/marketplace)<a href="https://agentmods.dev/plugins/data-wise/claude-plugins/marketplace"><img src="https://agentmods.dev/badge/plugins/data-wise/claude-plugins/marketplace/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/data-wise/claude-plugins/marketplace"><img src="https://agentmods.dev/badge/plugins/data-wise/claude-plugins/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
data-wise marketplace 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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "data-wise",
"owner": {
"name": "Data-Wise",
"email": "[email protected]"
},
"metadata": {
"description": "Aggregator marketplace for all Data-Wise Claude Code plugins \u2014 add once to receive every current and future plugin (Code + Desktop/Cowork).",
"version": "1.0.0"
},
"plugins": [
{
"name": "craft",
"source": {
"source": "github",
"repo": "Data-Wise/craft"
},
"description": "Full-stack developer toolkit for Claude Code (commands, agents, skills).",
"version": "4.8.0",
"homepage": "https://data-wise.github.io/craft/",
"repository": "https://github.com/Data-Wise/craft",
"license": "MIT",
"category": "development"
},
{
"name": "scholar",
"source": {
"source": "github",
"repo": "Data-Wise/scholar"
},
"description": "Statistical research, manuscript, and teaching toolkit.",
"version": "3.9.2",
"repository": "https://github.com/Data-Wise/scholar",
"license": "MIT",
"category": "research"
},
{
"name": "rforge",
"source": {
"source": "github",
"repo": "Data-Wise/rforge"
},
"description": "R-package ecosystem orchestration and CRAN-readiness toolkit.",
"version": "2.21.0",
"repository": "https://github.com/Data-Wise/rforge",
"license": "MIT",
"category": "development"
},
{
"name": "himalaya",
"source": {
"source": "git-subdir",
"url": "Data-Wise/himalaya-mcp",
"path": "himalaya-mcp-plugin",
"ref": "main"
},
"description": "Himalaya email plugin (MCP) for Claude Code \u2014 manage email from the CLI/agent.",
"version": "2.1.2",
"repository": "https://github.com/Data-Wise/himalaya-mcp",
"license": "MIT",
"category": "productivity"
},
{
"name": "folio",
"source": {
"source": "github",
"repo": "Data-The plugins it lists here
This marketplace lists 4 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 4d ago Changed 4880f7902cdb
- 11d ago Changed f8b680567b68
- 16d ago Changed 68f66b1ae53e
- 20d ago Changed fd8afa64435c
- 22d ago Changed 22d2af47f1b9
- 1mo ago Changed c0b9e015d5c4
- 1mo ago Changed 254a6cc1071a
- 1mo ago Changed · +2 lines 397ebf1eaa35
- 1mo ago Changed 3a9234d6537c
- 1mo ago First seen · 75 lines scan A e1467e967210
data-wise marketplace is a plugin published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 4d ago), licensed MIT. 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-31.
Other plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
superpowers
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques.