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/curiositech/some_claude_skillsWrote 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/curiositech/some_claude_skills/data-viz-2025)<a href="https://agentmods.dev/plugins/curiositech/some_claude_skills/data-viz-2025"><img src="https://agentmods.dev/badge/plugins/curiositech/some_claude_skills/data-viz-2025.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
data-viz-2025 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 yesterday.
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": "data-viz-2025",
"description": "State-of-the-art data visualization for React/Next.js/TypeScript with Tailwind CSS. Creates compelling, tested, and accessible visualizations following Tufte principles and NYT Graphics standards. Activate on \"data viz\", \"chart\", \"graph\", \"visualization\", \"dashboard\", \"plot\", \"Recharts\", \"Nivo\", \"D3\". NOT for static images, print graphics, or basic HTML tables."
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 93 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- yesterday First seen · 5 lines scan A a06cf438578c
data-viz-2025 is a plugin published in the GitHub repository curiositech/some_claude_skills (214 stars, last pushed yesterday), 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-09-06.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
experience-react
Build Salesforce React UI Bundle apps: scaffold a new React UI bundle SFDX starter project from a template, generate and edit pages, components, layout, styling, navigation, and branding with shadcn/ui and Tailwind CSS, configure ui-bundle metadata, host the app on a Digital Experience Site, and deploy it to an org.…
app-builder
Development, customization, testing, and deployment skills for Adobe App Builder projects, including the Workfront UI-extension suite (skills/appbuilder-workfront).
fuse-react
Expert React 19 with hooks, TanStack Router, Zustand, React Hook Form, Testing Library, shadcn/ui, and SOLID principles.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…
react-tips
React and JavaScript patterns for state management, performance, hooks, component design, avoiding unnecessary useEffects, and preferring ES2025/ES2026 APIs.