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-validation-offloadgit 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-validation-offload)<a href="https://agentmods.dev/skills/tutur3u/platform/tuturuuu-validation-offload"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-validation-offload/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-validation-offload"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-validation-offload.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.00024 | $0.00497 |
| Opus 5 | $0.00012 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
tuturuuu-validation-offload 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuturuuu Validation Offload
Core Workflow
Use this skill when validation work is heavy enough to distract from coding or when the user asks to test through devboxes. The goal is to keep local reasoning fast while still collecting trustworthy command evidence.
Read references/offload-playbook.md when choosing command boundaries,
timeouts, sequencing, or failure triage for devbox validation.
Decision Rules
Prefer devbox offload for:
bun checkand other repo-wide validation- package test suites that run for more than a short focused pass
- Docker, Supabase, or browser workflows that consume a lot of local resources
- repeated validation while implementation continues locally
Keep validation local when:
- the command must inspect a live local browser window or desktop UI
- the target depends on unsynced local-only state
- the run would mutate production or global machine state without explicit user approval
- the user asked for native/local reproduction specifically
Execution Pattern
Start with focused commands, then broaden:
- Quick runner smoke such as
bun --version. - Focused tests for the changed files.
- Package-level tests.
bun checkonly after narrower failures are resolved.
Split independent commands into separate runs so failures identify the owning
surface. Use explicit --timeout values and report run IDs, status, exit code,
and key log lines.
Failure Handling
Treat devbox-only failures as signal. Compare against a native focused run when the root cause is unclear, then inspect:
- cwd and checkout resolution
- config env var names, especially
TUTURUUU_CONFIG - inherited environment and secret leakage
- shell startup output that pollutes logs
- missing local services or mismatched Supabase targets
- runner version drift, fixed with
ttr box upgradeonly when requested
Do not hide a devbox-only failure just because a native command passes. Either fix the runner path or document the remaining devbox limitation.
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.
- 5d ago Changed · -32 tokens per session c392847b7a2c
- 8d ago First seen · 73 lines · 56 tokens per session scan A 24c8bda3ef3d
tuturuuu-validation-offload is a skill published in the GitHub repository tutur3u/platform (53 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 497 once invoked, about $0.0001 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
fix-ci
Fix the failed CI checks for the current session. Use when the user requests a CI fix via the Fix Checks button in the Changes toolbar.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
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.
vuestrata-quality-gates
Use when deciding the smallest correct verification set for a change in this repo.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.
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…