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/yonatangross/orchestkit/devnpx skills add yonatangross/orchestkit --skill devgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/dev)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/dev"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/dev.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.00076 | $0.03220 |
| Opus 5 | $0.00038 | $0.01610 |
| Sonnet 5 | $0.00015 | $0.00644 |
| Haiku 4.5 | $0.00008 | $0.00322 |
Grade A, and why
dev 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 yesterday.
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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ork:dev — Lab-Stack Boot
One command boots the four moving parts of a Vercel-Labs-flavored dev loop:
- portless → named HTTPS
https://<branch>.localhost(no port collisions across worktrees) - emulate → stateful API emulators on the same origin via
@emulators/adapter-next - dev server →
pnpm dev/npm run dev/yarn dev(auto-detected) - agent-browser → pre-warmed session named after the branch
State lives in .claude/state/dev-stack.json. Teardown via /ork:dev stop reads the PIDs and signals SIGTERM in reverse boot order.
Paired with
/ork:expect: the agent-browser session that/ork:devwarms is the same one/ork:expect(and the M125 #2 auto-trigger) attach to — no second startup latency on the first UI test.
When to invoke
| Situation | Command |
|---|---|
| Start work on a new branch | /ork:dev |
| Resume after a session break | /ork:dev (idempotent — skips already-live processes) |
| Tear down before deleting branch | /ork:dev stop |
| Inspect state | /ork:dev status |
| Share preview with stakeholder | /ork:dev --share (tailnet) or /ork:dev --funnel (public) |
| Time-boxed live demo | /ork:dev --live 4 (public funnel, 4-hour expiry) |
Resuming a backgrounded dev session (CC 2.1.144+): Sessions started via
claude --bgnow appear in/resumealongside interactive ones, markedbg— use/resumeas the direct recovery path after a crash or session end instead of navigating the agent view.Background shell sessions (CC 2.1.154+): In
claude agents, type! <command>to run a shell command as a backgrounded session you can attach to and detach from — also available asclaude --bg --exec '<command>'. Useful for long dev-loop processes (watchers, builds, servers) you want to monitor without holding a terminal.
Modes (M127)
| Flag | Wraps | Reach | Tailscale CLI |
|---|---|---|---|
| (none) | portless <slug> <pkg-mgr> run dev |
https://<branch>.localhost only |
not required |
--share |
portless --tailscale ... |
tailnet members on https://*.ts.net |
required |
--funnel |
portless --funnel ... |
public on the internet | required |
--live N |
portless --funnel ... + N-hour expiry |
public, tracked in live-demos.jsonl |
required |
What ships with it
12 files 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.
- references/boot-sequence.md 7.3 KB
- references/state-schema.md 4.1 KB
- rules/_sections.md 1.0 KB
- rules/_template.md 339 B
- rules/branch-named-subdomain.md 1.5 KB
- rules/idempotent-boot.md 1.7 KB
- rules/lab-stack-prerequisites.md 2.0 KB
- rules/teardown-order.md 1.8 KB
- scripts/boot.sh 17 KB runs code
- scripts/status.sh 2.7 KB runs code
- scripts/stop.sh 3.4 KB runs code
- test-cases.json 3.9 KB
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.
- yesterday First seen · 256 lines · 76 tokens per session scan A 968395cf86e0
dev is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 3,220 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
cli-usage
Complete reference for the systemprompt CLI - 8 domains, 64+ subcommands for managing AI infrastructure, services, agents, cloud deployments, and analytics.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
azure-resource-manager-durabletask-dotnet
Azure Resource Manager SDK for Durable Task Scheduler in .NET. Use for MANAGEMENT PLANE operations: creating/managing Durable Task Schedulers, Task Hubs, and retention policies via Azure Resource Manager. Triggers: "Durable Task Scheduler", "create scheduler", "task hub", "DurableTaskSchedulerResource", "provision…
azure-mgmt-fabric-dotnet
Azure Resource Manager SDK for Fabric in .NET. Use for MANAGEMENT PLANE operations: provisioning, scaling, suspending/resuming Microsoft Fabric capacities, checking name availability, and listing SKUs via Azure Resource Manager. Triggers: "Fabric capacity", "create capacity", "suspend capacity", "resume capacity"…