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/ruslan-korneev/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/ruslan-korneev/claude-plugins/linear)<a href="https://agentmods.dev/plugins/ruslan-korneev/claude-plugins/linear"><img src="https://agentmods.dev/badge/plugins/ruslan-korneev/claude-plugins/linear/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/ruslan-korneev/claude-plugins/linear"><img src="https://agentmods.dev/badge/plugins/ruslan-korneev/claude-plugins/linear.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linear 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 1mo 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": "linear",
"version": "2.0.0",
"description": "Linear integration: kanban board, cycle management, issue archive/delete, and comment edit/delete. Uses official Linear MCP for standard CRUD operations.",
"author": { "name": "Ruslan Korneev" },
"repository": "https://github.com/ruslan-korneev/claude-plugins",
"keywords": ["linear", "issues", "project-management", "kanban", "sprints", "cycles", "mcp"]
}
What it installs
The manifest is a name and a version. 1 skill, 4 commands, 1 agent, 1 MCP server travel with it, and installing the plugin installs all of them — 73 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.
- 1mo ago First seen · 9 lines scan A b423774e3e21
linear is a plugin published in the GitHub repository ruslan-korneev/claude-plugins (5 stars, last pushed 7mo 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
backlog
Project backlog manager — records deferred tasks into docs/backlogs/ only when the user asks, when the user picks the backlog for an unrelated bug or out-of-scope side task Claude found (the other offered options being fix-it-now and skip), or in a background session needing the user's decision. Never captures…
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
product-management
Product management specialists for PRD writing, content creation, and project planning. Tools for product managers and technical writers.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
radin
Cost-optimized agentic workflow stack for solo devs: backlog orchestration (radin-batch, radin-plan, radin-review) plus curated companion tools.
vp-beads
Sprint workflow automation: backlog grooming, retrospectives, upstream vendor tracking, cross-project synergy tracking, swarm wave orchestration, vendor sync, and bilateral sibling reconciliation for projects using beads and Basic Memory.