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 skills add Dankosik/go-service-template-rest --skill orchestratorgit clone --depth 1 https://github.com/Dankosik/go-service-template-restWrote 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/dankosik/go-service-template-rest/orchestrator)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/orchestrator"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/orchestrator/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/dankosik/go-service-template-rest/orchestrator"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/orchestrator.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.00030 | $0.00452 |
| Opus 5 | $0.00015 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
orchestrator 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 4d 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.
What it actually says
Ledger Orchestrator
Apply the Planning Ledger
Contract
and the current adapter selected by Agent
Harness. Treat tasks.md as a dependency
graph, not an ordered list.
Only this carrier writes canonical ledger state during orchestrated execution.
At each cycle, apply the contract's ready-frontier and capacity rules; dispatch
every ready unit to an acceptance-unit-lead before waiting, using only the
contract's permitted Lead reuse.
Process each Lead's immutable Acceptance Result
V1 through
the contract's acceptance transition. Integrate Implemented candidates
serially into the local development tree and immediately refill the frontier;
do not wait for tests or reviews. Route Blocked to recovery. After assembly,
assign one Lead the final delivery boundary, consume its final proof and
acceptance result, and record it without repeating validation.
Route the smallest upstream repair back to the same unit. Do not cancel unrelated running units when one unit reopens or discovers a lock. Apply Parent-Owned Recovery to technical, proof, review, and phase gaps; repair ledger status through Planning when needed. Continue until the ledger is done and Cleanup has closed execution-only state, or no ready unit, owner-held recovery, or authorized cleanup path remains.
Use the adapter's full-ledger carrier only when its required native identities, messaging, and wait controls are callable. Otherwise return that exact carrier gap before dispatch; never silently contract the ledger into a different workflow. Do not implement unit work or keep a parallel artifact, task, or Git journal.
What ships with it
1 file 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.
- 4d ago Changed · +3 lines 035f2b749ee2
- 5d ago Changed · -4 lines a6c083ad8e18
- 10d ago First seen · 46 lines · 30 tokens per session scan A ff01eaf96a76
orchestrator is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 452 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-31.
Other skills, from other repositories
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
readme-generate
A tool that analyzes source code to generate English and Chinese README files and related project documentation.
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
search-suitable-public-api
Search the curated Agenvoy public API list for an API that fits the current user need or skill context, then chain into the api-tool-add skill to register it under /.config/agenvoy/tools/api/. Triggers when the agent lacks a tool for a data lookup (weather, currency, geocoding, dictionary, etc.), when the user says…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…