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-tasksgit 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-tasks)<a href="https://agentmods.dev/skills/tutur3u/platform/tuturuuu-cli-tasks"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-cli-tasks.svg" alt="Measured on agentmods" 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.00023 | $0.01243 |
| Opus 5 | $0.00012 | $0.00622 |
| Sonnet 5 | $0.00005 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
tuturuuu-cli-tasks 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuturuuu CLI Tasks
Core Workflow
Use this skill when the user asks to add, create, template, track, split, list,
inspect, move, complete, or close Tuturuuu tasks through the native ttr CLI.
Inside the Tuturuuu monorepo, use the local script form:
bun ttr tasks --json --no-update-check
Outside the monorepo or after global installation, use ttr ... directly.
Use $tuturuuu-cli for CLI install, auth, session, version, or general SDK work.
Use $tuturuuu-commit when the user asks to commit task CLI changes.
Detailed examples live in
plugins/tuturuuu/skills/tuturuuu-cli-tasks/references/task-workflows.md.
Task Capture Requests
When a user asks to add, create, track, or split a Tuturuuu task, prioritize the
ttr CLI immediately. Do not substitute markdown TODOs, local notes, or GitHub
issues unless the user explicitly asks for those artifacts.
Discover current destinations before creating tasks:
ttr whoami --no-update-check
ttr boards --no-update-check
ttr lists --no-update-check
ttr labels --no-update-check
Create commands should support a quoted positional name as shorthand for
--name, especially ttr tasks create "Add Tuturuuu CLI".
For a combined task that should be split, create replacement tasks first, verify the new task keys, then close or otherwise mark the original as superseded.
Task Defaults
Read-oriented task-adjacent groups list by default:
ttr boardsttr labelsttr liststtr projectsttr task-templatesttr tasks
ttr tasks should show open tasks by default by excluding rows with
completed_at or closed_at. Keep --all, --done, --closed,
--include-done, --include-closed, and --compact intentional.
Compact task output is for agent workflows and should display only task title,
task list name, and workspace name unless the user asks for JSON. Human table
output should order by priority first, then due date, with readable due labels
such as Today, Tomorrow, or May 10.
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.
- yesterday Changed · -51 tokens per session 362536bc1adc
- 4d ago First seen · 158 lines · 74 tokens per session scan A 0cface1b6159
tuturuuu-cli-tasks is a skill published in the GitHub repository tutur3u/platform (53 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 1,243 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
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…
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
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.
react-query-setup
Set up @trpc/tanstack-react-query with createTRPCContext(), TRPCProvider, useTRPC() hook, queryOptions/mutationOptions factories, query invalidation via queryClient.invalidateQueries with queryFilter, and type inference with inferInput/inferOutput.
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.