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/LerianStudio/ringWrote 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/lerianstudio/ring/pm-team)<a href="https://agentmods.dev/plugins/lerianstudio/ring/pm-team"><img src="https://agentmods.dev/badge/plugins/lerianstudio/ring/pm-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/lerianstudio/ring/pm-team"><img src="https://agentmods.dev/badge/plugins/lerianstudio/ring/pm-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ring-pm-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 23d 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": "ring-pm-team",
"displayName": "Ring PM Team",
"description": "Pre-dev planning workflows: 4-gate and 8-gate orchestrators for PRD, TRD, OpenAPI contracts, schema design, and a phased plan. 14 skills + 4 research agents.",
"version": "1.0.0",
"author": {
"name": "Lerian Studio",
"email": "[email protected]"
},
"homepage": "https://github.com/lerianstudio/ring/tree/main/pm-team",
"repository": "https://github.com/lerianstudio/ring",
"license": "MIT",
"keywords": [
"skills",
"product",
"pre-dev",
"planning",
"prd",
"trd",
"api-design",
"data-model",
"workflow",
"feature-planning",
"phases-and-epics"
],
"skills": "./skills/",
"agents": "./agents/",
"hooks": "./hooks/hooks.json"
}
What it installs
The manifest is a name and a version. 14 skills, 4 agents travel with it, and installing the plugin installs all of them — 1,704 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill ring:creating-grafana-dashboards A 103 tokens
- Skill ring:writing-trds A 150 tokens
- Skill ring:mapping-streaming-events A 95 tokens
- Skill ring:mapping-feature-relationships A 104 tokens
- Skill ring:designing-api-contracts A 114 tokens
- Skill ring:designing-data-model A 120 tokens
- Skill ring:pinning-dependency-versions A 102 tokens
- Skill ring:planning-large-features A 89 tokens
- Skill ring:reconciling-predev-docs A 115 tokens
- Skill ring:validating-ux-completeness A 113 tokens
- Skill ring:planning-small-features A 85 tokens
- Skill ring:researching-features A 106 tokens
- Skill ring:writing-prds A 102 tokens
- Skill ring:using-pm-team A 100 tokens
- Agent ring:product-designer A 46 tokens
- Agent ring:docs-researcher A 56 tokens
- Agent ring:repo-researcher A 46 tokens
- Agent ring:web-researcher A 58 tokens
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.
- 23d ago First seen · 30 lines scan A 991768198a6f
ring-pm-team is a plugin published in the GitHub repository LerianStudio/ring (217 stars, last pushed today), 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-09-15.
Other plugins, from other repositories
claude-playbook
Engineering guardrails for Claude Code: path-scoped rules, review and verification skills, specialist subagents, and hooks that enforce what instructions only request.
easy-cheese
easy-cheese. Cheese your code 🧀 — high-quality results as easy as cheese. A portable, harness-agnostic Agent Skills toolkit.
yarbrain
A reviewable Markdown second brain for Codex and Claude Code.
shipwithai-starter
Sets up a standardized Claude Code harness for your project: CLAUDE.md, permissions, hooks, MCP servers, agents, SSOT docs, and observability logging. One init interview, consistent harness across every team member.
save-point
The 30-second comprehension check after every AI-assisted merge. Quiz yourself on the code you ship, with source-grounded questions, honest labels, and spaced recall.
essentials
24 commands, 8 agents. Loops, swarms, and teams powered by Claude Code's built-in Task System. Native task dependencies, ctrl+t progress, automatic persistence.