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-cli-resourcesgit 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-cli-resources)<a href="https://agentmods.dev/skills/tutur3u/platform/tuturuuu-cli-resources"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-cli-resources/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-cli-resources"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-cli-resources.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.00026 | $0.00691 |
| Opus 5.5 | $0.00010 | $0.00276 |
| Sonnet 5.5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
tuturuuu-cli-resources 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TTR Resource Control
Keep concurrent editing responsive by admitting heavy validation through one
per-user queue. Check ttr resources help and ttr resources status --json
before a broad test, build, type check, database setup, or browser suite.
These commands are local and require no login.
Choose execution
- Prefer a verified remote runner for broad validation:
ttr box run --runner <remote-id> -- <command>. Confirm its actual host and checkout; same-machine runners and containers do not offload CPU or RAM. - For local work, use
ttr resources run -- <command>. Sequence lint, tests, and browser QA. Do not start independent heavy commands with Promise.all, parallel shells, or background operators merely because separate threads own them. - Run focused checks first. The queue does not excuse skipping required checks. Persistent development servers and custom subprocess fan-out still consume resources; start only services needed for the task and clean up your own.
Setup and inspect
When machine setup is authorized, use:
ttr resources setup --root <repo> --shell zsh --dry-run
ttr resources setup --root <repo> --shell zsh
ttr resources status --json
Repeat --root for other repositories. Linked Git worktrees inherit repository
scope. Zsh/Bash hooks apply to new shells; --shell none avoids shell edits and
supports explicit queue use. Installation backs up shell files. Setup does not
modify repository source, Docker settings, credentials, or runner registrations.
The queue runs one job per user. Turbo runs one task; Vitest/Cargo workers adapt
to host RAM/CPU. Use --workers only for a justified override. Turbo task
concurrency alone does not cap Vitest's worker pool. Do not use separate
TTR_RESOURCES_HOME values across projects: that creates independent queues.
Elevated host memory pressure delays new admission. Keep the wait observable;
continue lightweight editing while it clears. Do not kill an owner, delete a
live lock, or routinely use TTR_RESOURCES_BYPASS=1 / --ignore-pressure to
avoid waiting. A bypass is a deliberate exception for a known small operation.
What ships with it
1 file 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 · -25 tokens per session 6336877c6fd5
- 1mo ago First seen · 67 lines · 51 tokens per session scan A d53b52340d47
tuturuuu-cli-resources is a skill published in the GitHub repository tutur3u/platform (55 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 691 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-12.
Other skills, from other repositories
integration-e2e-testing
Selects and designs the smallest integration/E2E test set that proves accepted behavior at an observable boundary. Use when writing or reviewing E2E or integration tests.
frontend-typescript-testing
Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present. Use when adding or reviewing component, loading/error-state, integration, or frontend E2E tests.
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.
agent-browser
Use the agent-browser CLI to exercise web interfaces, inspect rendered accessibility state, verify interactions, and capture screenshots. Use for browser-based UI testing and evidence collection. Do not use as a substitute for deterministic Playwright coverage when an automated regression test is the requested…
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.