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/qxbyte/pluginhubWrote 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/qxbyte/pluginhub/task-swarm)<a href="https://agentmods.dev/plugins/qxbyte/pluginhub/task-swarm"><img src="https://agentmods.dev/badge/plugins/qxbyte/pluginhub/task-swarm/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/qxbyte/pluginhub/task-swarm"><img src="https://agentmods.dev/badge/plugins/qxbyte/pluginhub/task-swarm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
task-swarm 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": "task-swarm",
"version": "0.13.0",
"description": "Standalone multi-agent orchestration via pipeline.yml (fork coders + reviewer/validator loops).",
"author": {
"name": "xueqiang",
"email": "[email protected]"
},
"homepage": "https://github.com/qxbyte/pluginhub",
"license": "MIT",
"keywords": [
"task-swarm",
"multi-agent",
"orchestration",
"pipeline"
]
}
What it installs
The manifest is a name and a version. 1 skill, 3 agents travel with it, and installing the plugin installs all of them — 327 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 Changed c0efa9fe4a3c
- 1mo ago First seen · 18 lines scan A 9a1e5dde678b
task-swarm is a plugin published in the GitHub repository qxbyte/pluginhub (3 stars, last pushed 25d 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
shinkoku
A Claude Code plugin for Japanese tax filing. It supports employees with side businesses, including business-income, blue-return, income-tax, and consumption-tax filings.
python-dev
Python development workflow with architecture design, coding guidelines, testing patterns, and specialized review agents.
elnora-platform
Elnora AI Platform CLI and skills.
persona
Switchable response personas with a shared token-reduction engine: bundled characters (holmes, genshijin, noctis, lunafreya, ignis), user-defined characters that survive plugin updates, three compression levels persisted across sessions, a persona-switch CLI other skills can call, character-agnostic…
team-comms
Asynchronous discussion between each team member's coding agent over a shared folder (Google Drive, OneDrive, file server). Immutable append-only threads make write conflicts structurally impossible; research is shared as attachments instead of hand-delivered documents; notifications are opt-in per working directory…
agent-ops
Run agents in a terminal multiplexer: herdr and Zellij setup, handoff between agents, role-based teams, persistent sidekicks, and the WSL/VS Code launch doctor. Install at user scope to make it available across all projects.