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.
/plugin marketplace add datascienceworld-kan/vinagentnpx agentmods add plugins/datascienceworld-kan/vinagent/claude-apigit clone --depth 1 https://github.com/datascienceworld-kan/vinagentWrote 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/datascienceworld-kan/vinagent/claude-api)<a href="https://agentmods.dev/plugins/datascienceworld-kan/vinagent/claude-api"><img src="https://agentmods.dev/badge/plugins/datascienceworld-kan/vinagent/claude-api.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-api 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 today.
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": "claude-api",
"description": "Claude API and SDK documentation skill for building LLM-powered applications",
"source": "./",
"strict": false,
"skills": [
"./skills/claude-api"
]
}What ships with it
1 file beside marketplace.json#claude-api 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.
- today First seen · 9 lines scan A 57e416b9eed0
claude-api is a plugin published in the GitHub repository datascienceworld-kan/vinagent (74 stars, last pushed 5mo 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-09-03.
Other plugins, from other repositories
AgentsMeetRL
Troubleshooter + machine-readable corpus for reinforcement-learning training, evaluation, and experiment design on LLM agents (single/multi-agent, multi-turn, tool-augmented). Distilled from the AgentsMeetRL awesome list (355 projects).
skill-heaven
Working prototype of Skill Heaven for Claude Code, actively tested for public use. One mechanic — /summon, one skill into context for one session, nothing installed — on one line: zero · low · med · high · xhigh · max · ultra, whose four surfaces are contiguous bands read from the current rung. /skill-zero is the…
humanizer
Rewrite AI-sounding text so it reads naturally 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.
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 98 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.