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 atretyak1985/swarmerynpx agentmods add plugins/atretyak1985/swarmery/jira-packgit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/jira-pack)<a href="https://agentmods.dev/plugins/atretyak1985/swarmery/jira-pack"><img src="https://agentmods.dev/badge/plugins/atretyak1985/swarmery/jira-pack.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jira-pack 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 2d 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": "jira-pack",
"description": "Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires core and an Atlassian MCP provider enabled on the machine.",
"version": "0.6.1",
"author": {
"name": "atretyak",
"email": "[email protected]"
}
}What it installs
The manifest is a name and a version. 7 skills, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 802 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill jira-delivery A 114 tokens
- Skill jira-triage A 95 tokens
- Skill jira-access-preflight A 111 tokens
- Skill jira-escalation A 112 tokens
- Skill jira-writeback A 94 tokens
- Skill swarmery-board-card A 130 tokens
- Skill jira-config A 54 tokens
- Command jira-fix A 50 tokens
- Agent jira-task-runner A 42 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.
- 2d ago First seen · 9 lines scan A 05a6f8110b7b
jira-pack is a plugin published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed yesterday), 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-03.
Other plugins, from other repositories
code-quality
Code quality pipeline — SOLID refactoring, TDD workflow, design patterns, performance optimization, and 6 specialist review agents.
implementation
Disciplined implementation stage: execute approved plans inline (/implementation:implement) or via orchestrated worker subagents (/implementation:implement-dispatch) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back.
tdd-core
Language-agnostic TDD methodology: Red-Green-Refactor cycle, Arrange-Act-Assert, testing strategy, anti-patterns.
anvil-pulse
Live operator dashboard for long autonomous anvil runs: claims, phases, lease countdowns, event feed, and stuck-state detection served as a local web page, plus an optional Claude Code statusline segment.
cli-to-plugin
Convert any CLI tool into a self-contained Claude Code plugin by walking its --help tree and generating one skill per command group, plus optional LLM-proposed workflow meta-skills.
fakoli-flow
Intent-driven workflow orchestration — brainstorm, plan, and execute complex projects through coordinated specialist agents with critic gates and evidence-based verification.