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 tutur3u/platform --skill tuturuuu-devbox-opsgit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/tuturuuu-devbox-ops)<a href="https://agentmods.dev/skills/tutur3u/platform/tuturuuu-devbox-ops"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-devbox-ops/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/tutur3u/platform/tuturuuu-devbox-ops"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-devbox-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00620 |
| Opus 5.5 | $0.00010 | $0.00248 |
| Sonnet 5.5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
tuturuuu-devbox-ops 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 1mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuturuuu Devbox Ops
Core Workflow
Use this skill for operational work around Tuturuuu devboxes: ttr box setup,
runner registration, one-shot agents, 24/7 services, smoke tests, upgrades, and
admin observability.
Start by identifying the target:
- Local app/local Supabase: use the repo-local CLI with
TUTURUUU_CONFIG=<config-file> bun ttr .... - Installed CLI/global profile: use
ttr .... - Production or another environment: verify the base URL and never assume the local config file is active.
Read references/devbox-ops-checklist.md for the concrete queue-and-claim
smoke flow, cleanup SQL shape, service setup expectations, and common gotchas.
Safety Rules
- Never print, commit, or paste runner tokens. Refer to token files or env vars by path/name only.
- Prefer
--json --no-update-checkfor machine-readable runs. - Use temporary runner names for smoke tests and clean them up before handoff.
- Cleanup must delete runner token rows and then mark the runner revoked.
- Treat same-machine runner execution as brokered execution validation, not proof of container isolation.
- If a devbox failure only appears under the agent, inspect cwd, env isolation, shell startup files, config path, and runner token source before dismissing it as a flaky test.
Setup Guidance
For a long-lived machine, prefer:
ttr box setup --dir . --agent --service --runner-name "$(hostname)-devbox" --yes
For current-checkout validation, prefer a one-shot agent loop:
- Register a temporary runner.
- Queue one command with
ttr box run --runner <runner-id> ... -- <command>. - Start
ttr box agent start --once. - Verify run JSON has
status: "succeeded"andexitCode: 0. - Cleanup token rows and mark the runner revoked.
Use ttr box upgrade --runner <runner-id> only when the operator wants to
mutate the installed CLI on that runner.
Use ttr box serve or ttr box tunnel for long-running preview work. Pass
Cloudflare tunnel tokens by local environment variable name with
--cloudflared-token-env; never paste raw tunnel tokens into commands or docs.
Use --database-url-env when an app devbox should connect to a database hosted
by another devbox.
What ships with it
2 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.
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.
- 1mo ago Changed · -39 tokens per session a10133d58a93
- 1mo ago First seen · 69 lines · 64 tokens per session scan A 40c240492807
tuturuuu-devbox-ops is a skill published in the GitHub repository tutur3u/platform (55 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 620 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-09-03.
Other skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
frontend-engineer
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults" !cat .forgewright/codebase-context.md…
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
subscriptions
Set up real-time event streams with async generator subscriptions using .subscription(async function() { yield }). SSE via httpSubscriptionLink is recommended over WebSocket. Use tracked(id, data) from @trpc/server for reconnection recovery with lastEventId. WebSocket via wsLink and createWSClient from @trpc/client…
links
Configure the tRPC client link chain: httpLink, httpBatchLink, httpBatchStreamLink, splitLink, loggerLink, wsLink, createWSClient, httpSubscriptionLink, unstablelocalLink, retryLink. Choose the right terminating link. Route subscriptions via splitLink. Build custom links for SOA routing. Link options: url, headers…