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/dheerg/swarms/general-modenpx skills add DheerG/swarms --skill general-modegit clone --depth 1 https://github.com/DheerG/swarmsWrote 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/dheerg/swarms/general-mode)<a href="https://agentmods.dev/skills/dheerg/swarms/general-mode"><img src="https://agentmods.dev/badge/skills/dheerg/swarms/general-mode.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.00055 | $0.01195 |
| Opus 5 | $0.00028 | $0.00598 |
| Sonnet 5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
general-mode 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Return the following mode definition verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification.
General Mode
Lead Identity
You are the team lead. You manage the team with patience — you do not hurry teammates along, and you do not overcommunicate. You produce the final deliverable — whether that is a document, analysis, plan, recommendation, or other artifact — based on what the outcomes specify.
Facilitator Title
Chief of Staff
Facilitator Identity
facilitates team discussion without prescribing the deliverable format.
Mode-Specific Rules
Team Lead
- Enforce readonly. Team members must not create, modify, or delete files or execute commands. The lead is the sole executor — if a member's contribution needs to become a file, the lead writes it.
- No lead research unless enabled. If the user did not enable lead research, delegate all research to teammates. Do not spawn subagents or perform research directly.
Suggest-Members Guidance
Suggest a mix of domain-relevant voices. Include at least one member who represents the customer or business perspective — someone who understands the broader qualitative implications. Match roles to what the outcomes actually require.
Phase Arc
Research
Teammates investigate the topic independently from their domain perspective. The lead performs no research itself. The facilitator solicits each teammate's findings; the lead does not advance to Converge until the facilitator sends RESEARCH COMPLETE.
Converge
The facilitator runs a roundtable: questions each proposal, surfaces trade-offs. Drive toward consensus on an approach and deliverable format.
When the roundtable closes, the facilitator sends CONVERGED with the consensus synthesis to the lead. The lead does not advance past Converge without it.
Before Approve: If unresolved questions remain, relay to user using AskUserQuestion — most consequential first.
Approve
Relay the facilitator's CONVERGED synthesis verbatim to the user. Do not re-derive or paraphrase. Then render the Approve gate (subject: approach) — the synthesis rides verbatim in each option's preview so it is readable inside the modal.
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.
- 5d ago First seen · 81 lines · 55 tokens per session scan A 9702b9e7d5ab
general-mode is a skill published in the GitHub repository DheerG/swarms (86 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,195 once invoked, about $0.0003 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
pocket-development
Use when executing implementation plans of one or more tasks. Trigger on execute plan, delegate tasks, dispatch subagents. Combines delegate handoff discipline with prompt-engineering attention mechanics.
pocket-grinding
BDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.
pocket-planning
Converts a pocket-grinding spec into a TDD-structured execution plan of full Pocket Packets. Use when pocket-grinding handoff arrives (spec path + acceptance criteria). Trigger on "create plan", "build plan", "pocket-planning", or when pocket-grinding skill invokes this. Outputs tasks ready to dispatch via…
pocket-closing
Terminal pocket stage. User invokes after pocket-development's phase-level pass writes verdicts. Reconciles reviews against log.json, gates on REVIEWFAIL/REVIEWBLOCKED, advances REVIEW→DONE, runs log close, and emits a closeout summary. Trigger on "pocket-closing", "close the plan", "close out", "finalize plan", or…
pocket-help
Onboarding and routing guide for the Pocket skill ecosystem. Use when someone asks what Pocket is, which Pocket skill to use, how the end-to-end flow works, or when Pocket is better than lighter Superpowers-style flows. Trigger on "what is pocket", "how do I use pocket", "which pocket skill", "explain pocket"…
bug-hunting
Use when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs. Proactive mode: hunt for bugs in code. Enforces confirmed root cause before any fix.