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/sodam-ai/SoDam-AgentWrote 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/sodam-ai/sodam-agent/research-team)<a href="https://agentmods.dev/plugins/sodam-ai/sodam-agent/research-team"><img src="https://agentmods.dev/badge/plugins/sodam-ai/sodam-agent/research-team/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/sodam-ai/sodam-agent/research-team"><img src="https://agentmods.dev/badge/plugins/sodam-ai/sodam-agent/research-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
research-team 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 8d 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": "research-team",
"description": "리서치팀 — 수집(researcher) → 분석(analyst) → 반증(critic). SoDam-Agent 자체 큐레이션.",
"version": "0.1.1",
"author": { "name": "SoDam AI Studio" },
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 3 agents, 1 MCP server travel with it, and installing the plugin installs all of them — 36 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.
- 8d ago First seen · 8 lines scan A 18ae8cddf1f8
research-team is a plugin published in the GitHub repository sodam-ai/SoDam-Agent (18 stars, last pushed 29d 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
badi
Workflow management for Claude Code, Cursor, Gemini, Windsurf, AGENTS.md — 30 AI agents, 86 commands, 14 hooks, 63 opt-in skill categories. Built for Anthropic Claude Opus 4.7 and Sonnet 4.6.
cc-safe-setup
909 safety hooks for Claude Code — prevent file deletion, credential leaks, git disasters, and token waste during autonomous AI coding sessions.
hello-world
A simple example plugin that demonstrates basic Claude Code plugin functionality.
skillpack
Generate and verify the agent-distribution layer for any OSS project.
agentclaim
File ownership for parallel AI agents in one git working tree. Stops them silently overwriting each other.
synapse
MCP server and CLI for host and container operations: Docker and Compose control, SSH, host inspection, logs, ZFS, and safe file transfer.