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/unbound-force/gaze/forge-coordinationnpx skills add unbound-force/gaze --skill forge-coordinationgit clone --depth 1 https://github.com/unbound-force/gazeWrote 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/unbound-force/gaze/forge-coordination)<a href="https://agentmods.dev/skills/unbound-force/gaze/forge-coordination"><img src="https://agentmods.dev/badge/skills/unbound-force/gaze/forge-coordination.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.00011 | $0.00582 |
| Opus 5 | $0.00005 | $0.00291 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
forge-coordination 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Coordination
Patterns for coordinating parallel agent work.
Coordinator Protocol
- Initialize:
comms_init(project_path=".", task_description="...") - Check learnings:
hivemind_find(query="<task keywords>") - Select strategy:
forge_get_strategy_insights(task="<task>") - Decompose:
forge_decompose(task="<task>", context="<learnings>") - Create epic:
org_create_epic(epic_title="<task>", subtasks=[...]) - Spawn workers:
forge_spawn_subtask(bead_id, epic_id, subtask_title, files) - Monitor:
comms_inbox()+forge_status(epic_id, project_key) - Review:
forge_review(task_id, files_touched)for each worker - Complete:
forge_complete(bead_id, summary, files_touched) - Learn:
hivemind_store(information="...", tags="forge,<topic>")
Worker Protocol
- Initialize:
comms_init(project_path=".", task_description="...") - Check learnings:
hivemind_find(query="<task keywords>") - Reserve files:
comms_reserve(paths=[...], reason="...") - Implement: Make changes to reserved files
- Report progress:
forge_progress(bead_id, progress_percent, status) - Store learnings:
hivemind_store(information="...", tags="...") - Complete:
forge_complete(bead_id, summary, files_touched)
File Reservation Rules
- Workers MUST reserve files before editing
- Coordinators NEVER reserve files
- Use
comms_reserve(paths=[...], exclusive=true)for exclusive access - Release files when done:
comms_release(paths=[...]) - Emergency release:
comms_release_all()(coordinator only)
Progress Reporting
Report at milestones: 25%, 50%, 75%, 100%
forge_progress(
project_key="replicator",
agent_name="worker-1",
bead_id="<id>",
status="in_progress",
progress_percent=50,
message="Implemented core logic, starting tests"
)
Conflict Resolution
If a file reservation fails:
- Check who holds the reservation
- Send a message via
comms_sendto negotiate - Wait for release or escalate to coordinator
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 · 63 lines · 11 tokens per session scan A 3179f4fbb9fd
forge-coordination is a skill published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 582 once invoked, about $0.0001 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
hive-mind-advanced
Advanced Hive Mind collective intelligence system for queen-led multi-agent coordination with consensus mechanisms and persistent memory.
agent-teams
Coordinates Claude agent teams via filesystem protocol. Use when orchestrating parallel agents with task dependencies. Do not use for single-agent tasks.
orchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
agent-orchestration
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
sema-usage
Content-addressed vocabulary protocol via the sema MCP server. Use when working with shared vocabulary — searching, resolving, minting, and verifying meaning across agents and conversations.
cross-agent-handoff
Transfer context between AI agent sessions with structured handoff protocols, state serialization, and decision log preservation. Covers multi-agent coordination, context compression, and continuity patterns. Triggers on agent handoff, session transfer, or multi-agent continuity requests.