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/tta-lab/ttal-cli/setupnpx skills add tta-lab/ttal-cli --skill setupgit clone --depth 1 https://github.com/tta-lab/ttal-cliWhat 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.00036 | $0.01192 |
| Opus 5 | $0.00018 | $0.00596 |
| Sonnet 5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
setup 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 2d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TTAL Setup
Run setup steps automatically. Only pause when user action is required (Telegram bot creation, pasting tokens). Fix things yourself when possible.
Principle: Do the work. Only ask the user when you genuinely need their input (secrets, choices).
UX Note: Use AskUserQuestion for all user-facing questions.
Context
This skill runs inside the ttal-cli repository. All documentation is available
in docs/ (VitePress site) and templates are in templates/. When the user asks
questions about ttal, read from docs/ directly — no network requests needed.
1. Install ttal
Check if ttal is installed:
which ttal && echo "TTAL_OK=true" || echo "TTAL_OK=false"
If TTAL_OK=false, detect platform and install:
- macOS:
brew tap tta-lab/ttal && brew install ttal - Linux/other:
go install github.com/tta-lab/ttal-cli@latest- If
gonot found:brew install go(macOS) or guide user to install Go
- If
Verify: ttal version
2. Run ttal onboard
ttal onboard handles everything: prerequisites (tmux, taskwarrior, ffmpeg), workspace scaffold, taskwarrior UDAs, daemon install, worker hooks. When it runs ttal init, templates are found locally in this repo — no network clone needed. Just run it:
ttal onboard
If onboard reports fixable issues, re-run with ttal onboard --fix. Parse its output for any errors that need user attention.
After onboard completes, capture workspace path and verify team_path points to current directory:
WORKSPACE=$(pwd)
grep "team_path" ~/.config/ttal/config.toml
If team_path doesn't match current workspace, update it using perl -i -pe (portable across macOS and Linux):
perl -i -pe "s|team_path = .*|team_path = \"$WORKSPACE\"|" ~/.config/ttal/config.toml
3. Telegram Bot Setup (Optional)
AskUserQuestion: "Would you like to set up Telegram integration? This lets you manage agents from your phone. (You can skip this and add it later.)"
If yes:
3a. Get chat_id
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.
- 2d ago First seen · 153 lines · 36 tokens per session scan A 122a0a8f1736
setup is a skill published in the GitHub repository tta-lab/ttal-cli (23 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,192 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…