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.
npx agentmods add skills/qgolem/orc/swarmnpx skills add qGolem/orc --skill swarmgit clone --depth 1 https://github.com/qGolem/orcWrote 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/qgolem/orc/swarm)<a href="https://agentmods.dev/skills/qgolem/orc/swarm"><img src="https://agentmods.dev/badge/skills/qgolem/orc/swarm.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00009 | $0.02251 |
| Opus 5 | $0.00005 | $0.01125 |
| Sonnet 5 | $0.00002 | $0.00450 |
| Haiku 4.5 | $0.00001 | $0.00225 |
Grade A, and why
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 3d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Plan
Design a multi-agent team plan for an implementation task. Enters plan mode, explores the codebase, selects agent roles, writes task breakdowns with prompts, and exits for user approval.
Input
- $ARGUMENTS — Task description (e.g., "build phase 4 of user-vaults", "implement auth middleware")
Agent Roster
Available agent types for teammates. Choose based on what each task requires:
| Agent Type | Tools | Best For |
|---|---|---|
orc:orc-executor |
Read, Write, Edit, Bash, Glob, Grep, Task, Skill, SendMessage, TaskCreate, TaskUpdate, TaskList | Sequential task implementation with per-task commits |
orc:orc-impl-verifier |
Read, Write, Glob, Grep, Bash, Task, Skill, SendMessage, TaskCreate, TaskUpdate, TaskList | Verifying must_haves, running tsc/build, code review |
orc:frontend-verifier |
All tools | Browser testing (Agent Browser), visual QA, UI polish, CSS fixes |
general-purpose |
All tools | Flexible — anything that doesn't fit a specialized type |
orc:build-error-resolver |
Read, Write, Edit, Bash, Grep, Glob | Fixing tsc/build errors with minimal diffs |
Selection heuristics:
- Implementation work →
orc:orc-executor(commits per task, follows PLAN.md) - Verification gate →
orc:orc-impl-verifier(3-level checks against spec) - Frontend with UI → add
orc:frontend-verifierafter verification passes - Default model:
opusfor all teammates (strongest reasoning)
Execution
Step 1: Enter Plan Mode
Call EnterPlanMode. All subsequent work happens in plan mode (read-only except the plan file).
Step 2: Explore
Launch 1-3 Explore agents in parallel to understand:
- Scope: What files exist, what needs to be created, what needs to be modified
- Patterns: Existing code to mirror (find the closest analog for each new file)
- Spec: Read any existing plan/spec docs referenced in the task description
- Constraints: ABI signatures, type definitions, pitfall docs, test patterns
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 206 lines · 9 tokens per session scan A e451152e7787
swarm is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 2,251 once invoked, about $0.0000 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-31.
Other skills, from other repositories
finding-duplicate-functions
Use when auditing a codebase for semantic duplication — functions that do the same thing but have different names or implementations, especially common in LLM-generated codebases.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…