Borrowing it
Nothing to install: this file belongs to brake71/1c-ssl-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brake71/1c-ssl-skills/main/.agents/skills/multi-agent-patterns/SKILL.mdgit clone --depth 1 https://github.com/brake71/1c-ssl-skillsWrote 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/brake71/1c-ssl-skills/multi-agent-patterns)<a href="https://agentmods.dev/skills/brake71/1c-ssl-skills/multi-agent-patterns"><img src="https://agentmods.dev/badge/skills/brake71/1c-ssl-skills/multi-agent-patterns/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/brake71/1c-ssl-skills/multi-agent-patterns"><img src="https://agentmods.dev/badge/skills/brake71/1c-ssl-skills/multi-agent-patterns.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00042 | $0.03375 |
| Opus 5.5 | $0.00017 | $0.01350 |
| Sonnet 5.5 | $0.00008 | $0.00675 |
| Haiku 4.5 | $0.00004 | $0.00337 |
Grade A, and why
multi-agent-patterns 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 17d 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.
This is a copy
100% identical to multi-agent-patterns — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Architecture Patterns
Multi-agent architectures distribute work across multiple language model instances, each with its own context window. When designed well, this distribution enables capabilities beyond single-agent limits. When designed poorly, it introduces coordination overhead that negates benefits. The critical insight is that sub-agents exist primarily to isolate context, not to anthropomorphize role division.
When to Activate
Activate this skill when:
- Single-agent context limits constrain task complexity
- Tasks decompose naturally into parallel subtasks
- Different subtasks require different tool sets or system prompts
- Building systems that must handle multiple domains simultaneously
- Scaling agent capabilities beyond single-context limits
- Designing production agent systems with multiple specialized components
Do not activate this skill for adjacent work owned by other skills:
- Deciding task-model fit, pipeline shape, or project-level cost before topology is known:
project-development. - Designing hosted sandboxes, warm pools, remote sessions, or background runtime infrastructure:
hosted-agents. - Sharing orchestrator state through KV-cache compaction in controlled runtimes:
latent-briefing. - Designing the tools each agent exposes:
tool-design.
Core Concepts
Use multi-agent patterns when a single agent's context window cannot hold all task-relevant information. Context isolation is the primary benefit — each agent operates in a clean context without accumulated noise from other subtasks, preventing the telephone game problem where information degrades through repeated summarization.
Choose among three dominant patterns based on coordination needs, not organizational metaphor:
- Supervisor/orchestrator — Use for centralized control when tasks have clear decomposition and human oversight matters. A single coordinator delegates to specialists and synthesizes results.
- Peer-to-peer/swarm — Use for flexible exploration when rigid planning is counterproductive. Any agent can transfer control to any other through explicit handoff mechanisms.
- Hierarchical — Use for large-scale projects with layered abstraction (strategy, planning, execution). Each layer operates at a different level of detail with its own context structure.
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.
- 17d ago First seen · 268 lines · 42 tokens per session scan A 786ff9345eb4
multi-agent-patterns is a skill published in the GitHub repository brake71/1c-ssl-skills (82 stars, last pushed 15d ago), licensed MIT. It adds 42 tokens to every session and 3,375 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to multi-agent-patterns, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
form-compile
A form generator for managed 1C applications. It creates Form.xml from a JSON description or from an object's 1C metadata, such as a catalogue or document.
skd-edit
A focused editor for 1C data composition schemas, the report definitions that describe queries, fields, filters, totals, and parameters. It changes an existing Template.xml file through specific operations.
form-edit
A tool for modifying an existing managed form in 1C by adding screen elements, fields, commands, and event handlers. Event handlers are code routines that run when something happens, such as a field changing.
cfe-borrow
A tool for borrowing existing 1C configuration objects into an extension, so the extension can alter or add to those objects.
cfe-patch-method
A generator for method interceptors in 1C extensions, which let an extension add code before or after an existing method or replace its body. It reads the original method and creates or updates the required BSL source file.