Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmylchreest/aidenpx agentmods add skills/jmylchreest/aide/swarm-statusWrote 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/skills/jmylchreest/aide/swarm-status)<a href="https://agentmods.dev/skills/jmylchreest/aide/swarm-status"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/swarm-status/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/skills/jmylchreest/aide/swarm-status"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/swarm-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.00718 |
| Opus 5 | $0.00018 | $0.00359 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
swarm-status 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swarm Status
Quick orchestrator-side inspection of a live swarm. Run this when you want to see what your spawned subagents are doing right now without halting them or opening the aide-web dashboard.
Steps
1. Resolve current session (your own)
./.aide/bin/aide reflect current-session
Use that ID as <parent> below — it's the orchestrator session that owns
the swarm.
2. List agents in this swarm
./.aide/bin/aide agent list --parent=<parent> --json
Returns one record per registered subagent with parent_session,
namespace, status, halt, paused, deadline.
3. Active tasks for this swarm
./.aide/bin/aide task list --parent-session=<parent> --json
Filters the project-wide task bucket to ones tagged with this swarm's
parent. Look for tasks stuck in claimed without progress.
4. Recent messages
./.aide/bin/aide message list --parent-session=<parent>
Cross-agent comms within this swarm. High-priority messages from the orchestrator are surfaced to subagents on their next tool call by the signals hook.
5. Summarise for the user
Group by agent. For each, report:
- Status (running / paused / halted)
- Current tool (read
agent:<id>:currentToolviaaide state get currentTool --agent=<id>if you want this) - Any flags (halt with reason, pause)
- Open tasks they hold
- Deadline if set
Example output:
Swarm <parent-id-short> — 3 agents
agent-auth (running):
current: Edit src/auth/handler.ts
tasks: 2 in_progress
no flags
agent-payments (paused):
reason: scope drift — investigating
tasks: 1 claimed (#42)
paused 3m ago
agent-docs (halted):
reason: repeated rustdoc — see new instinct
halted 12m ago
When to use halts vs. messages
- Halt if the agent is clearly off-track or burning budget with no progress. The halt blocks tool calls; the model will respond once with the halt reason then stop.
- High-priority message if you want to redirect without stopping —
arrives as
additionalContexton the next tool call so the model can read it and adjust.
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.
- 11d ago First seen · 108 lines · 36 tokens per session scan A 3fcf49057f79
swarm-status is a skill published in the GitHub repository jmylchreest/aide (17 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 718 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…