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/bugrabilge/bilge-development-kit/orchestratenpx skills add bugrabilge/bilge-development-kit --skill orchestrategit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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.00045 | $0.01891 |
| Opus 5 | $0.00023 | $0.00945 |
| Sonnet 5 | $0.00009 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
orchestrate 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 2d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Agent Orchestration
You are now in ORCHESTRATION MODE. Your task: coordinate specialized agents to solve this complex problem.
Task to Orchestrate
$ARGUMENTS
🔴 CRITICAL: Minimum Agent Requirement
⚠️ ORCHESTRATION = MINIMUM 3 DIFFERENT AGENTS
If you use fewer than 3 agents, you are NOT orchestrating - you're just delegating.
Validation before completion:
- Count invoked agents
- If
agent_count < 3→ STOP and invoke more agents- Single agent = FAILURE of orchestration
Agent Selection Matrix
| Task Type | REQUIRED Agents (minimum) |
|---|---|
| Web App | frontend-specialist, backend-specialist, test-engineer |
| API | backend-specialist, security-auditor, test-engineer |
| UI/Design | frontend-specialist, seo-specialist, performance-optimizer |
| Database | database-architect, backend-specialist, security-auditor |
| Full Stack | project-planner, frontend-specialist, backend-specialist, devops-engineer |
| Debug | debugger, explorer-agent, test-engineer |
| Security | security-auditor, penetration-tester, devops-engineer |
Pre-Flight: Mode Check
| Current Mode | Task Type | Action |
|---|---|---|
| plan | Any | ✅ Proceed with planning-first approach |
| edit | Simple execution | ✅ Proceed directly |
| edit | Complex/multi-file | ⚠️ Ask: "This task requires planning. Switch to plan mode?" |
| ask | Any | ⚠️ Ask: "Ready to orchestrate. Switch to edit or plan mode?" |
🔴 STRICT 2-PHASE ORCHESTRATION
PHASE 1: PLANNING (Sequential - NO parallel agents)
| Step | Agent | Action |
|---|---|---|
| 1 | project-planner |
Create docs/PLAN.md |
| 2 | (optional) explorer-agent |
Codebase discovery if needed |
🔴 NO OTHER AGENTS during planning! Only project-planner and explorer-agent.
⏸️ CHECKPOINT: User Approval
After PLAN.md is complete, ASK:
"✅ Plan created: docs/PLAN.md
Do you approve? (Y/N)
- Y: Start implementation
- N: I'll revise the plan"
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.
- 2d ago First seen · 245 lines · 45 tokens per session scan A dfe7ca47922b
orchestrate is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,891 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
agent-messaging
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).
agento11y-prod-setup
Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the agento11y skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx…