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 jackfranklin/dotfiles --skill implement-orchestrategit clone --depth 1 https://github.com/jackfranklin/dotfilesWrote 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/jackfranklin/dotfiles/implement-orchestrate)<a href="https://agentmods.dev/skills/jackfranklin/dotfiles/implement-orchestrate"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/implement-orchestrate/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/jackfranklin/dotfiles/implement-orchestrate"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/implement-orchestrate.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.00033 | $0.01223 |
| Opus 5.5 | $0.00013 | $0.00489 |
| Sonnet 5.5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
implement-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 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate an Approved Plan
Read ~/.claude/skills/implement-plan/SKILL.md first. Every rule and workflow step in it applies unchanged; it is the single source of truth for scope, branching, testing, simplicity, commits, PRs, and the final report. This skill changes only who does the work: you are the orchestrator, sub-agents are the hands and the fresh eyes.
Invoking this skill is the user's explicit authorization to spawn sub-agents.
Orchestrator rules
- You own Git. Only you branch, stage, commit, push, and open the PR. Sub-agents edit files and nothing else — tell every implementer: "Do not run any git command that changes state."
- Trust nothing reported. A sub-agent saying "tests pass" or "done" is a claim, not evidence. Before accepting a task you run the verification commands yourself and read the full diff.
- Serial by default. Implement tasks one at a time in the shared worktree. Run implementers in parallel only when the plan marks tasks independent and their file sets are disjoint; give each
isolation: "worktree"and merge their results yourself, one task at a time. - The plan is the scope boundary — for reviewers too. A finding is fixed now only if it is a defect, a plan violation, a missing test the plan requires, or a verified high-value documentation finding within the changed behavior. Anything else, however good, is deferred to the final report.
code-revieweranddocumentation-reviewerapply distinct correctness and documentation lenses; you verify their findings again in triage. - Bounded loops. At most two review → fix rounds per task. If the third review still has fix-now findings, stop and escalate to the user with the outstanding findings.
- Escalate blockers, don't absorb them. Sub-agents cannot ask the user. When one returns
BLOCKED: <question>, answer it only if the plan or repository evidence settles it; otherwise apply implement-plan rule 2 and ask the user.
Workflow
1. Preflight and branch
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 Changed · -6 lines 8ac52b24ebbe
- 14d ago First seen · 71 lines · 33 tokens per session scan A 6784af5de6e2
implement-orchestrate is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 1,223 once invoked, about $0.0001 per session on Opus 5.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-10-11.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.