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 sanky369/vibe-building-skills --skill orchestratorgit clone --depth 1 https://github.com/sanky369/vibe-building-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/sanky369/vibe-building-skills/orchestrator)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/orchestrator"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/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/sanky369/vibe-building-skills/orchestrator"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/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.00179 | $0.01876 |
| Opus 5 | $0.00089 | $0.00938 |
| Sonnet 5 | $0.00036 | $0.00375 |
| Haiku 4.5 | $0.00018 | $0.00188 |
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 12d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creative Orchestrator
Route multi-asset creative work through the right skills in the right order, so style gets decided once and every downstream asset inherits it. Prime rule: strategy before pixels. Never let generation start before a style anchor exists — assets generated pre-brief get regenerated. You are a dispatcher, not a lecturer: diagnose fast, pick one route, name what each step hands to the next.
When to use / when not to
Use when the request spans multiple asset types, names an outcome rather than an
asset ("launch assets", "brand refresh", "content for the month"), or the right
skill is ambiguous. Do NOT use for a single clear asset — route directly:
one logo → skills/creative/brand-asset; one product shot →
skills/creative/product-photography; one Instagram post →
skills/creative/social-graphics; one generic image →
skills/creative/image-generation.
Intake (diagnostic — one batch)
- Outcome — what event/goal are these assets for (launch, rebrand, ongoing content, storefront, video)?
- What exists — style guide or Creative Direction Brief? Logo/brand assets? Product photos? (Existing artifacts skip their producing step.)
- Deliverables & destinations — which assets, where they'll live (platforms, store, site)?
- Automation — is
FAL_API_KEY(orFAL_KEY) set? If unknown, check:python docs/creative_cli.py test
Don't stall: with the outcome known, infer the rest from context, state assumptions, and present the plan. If automation is unavailable, the plan still runs — every step's deliverable becomes prompt specs plus runnable commands instead of generated files.
Routing table
Pick ONE route by the first rule that matches. Sequence is by dependency; each arrow names the artifact passed forward.
Decision rules
- No style anchor exists and >1 asset is needed → every route below starts with
skills/creative/creative-strategist. - Brand marks are among the deliverables →
brand-assetruns before any skill that reuses the marks. - Video deliverables → stills first (they are the video's source material).
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.
- 12d ago First seen · 131 lines · 179 tokens per session scan A a8b8afc4d9b9
orchestrator is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 179 tokens to every session and 1,876 once invoked, about $0.0009 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
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
zh-readme
A tool for writing README files in Chinese after first examining a software project. A README is the main guide visitors see when they open a code repository.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.