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/tanattv/lyt/lytnpx skills add TanaTTV/lyt --skill lytgit clone --depth 1 https://github.com/TanaTTV/lytWrote 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/tanattv/lyt/lyt)<a href="https://agentmods.dev/skills/tanattv/lyt/lyt"><img src="https://agentmods.dev/badge/skills/tanattv/lyt/lyt.svg" alt="Measured on agentmods" 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.00046 | $0.00588 |
| Opus 5 | $0.00023 | $0.00294 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
lyt 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use lyt for local media
lyt is a local CLI around yt-dlp and ffmpeg. Only download media the user owns
or has permission to use. A public URL does not automatically grant permission.
Find or install the command
- Try
lyt --version. - In the lyt repository, use
node bin/lyt.js. - Otherwise ask before globally installing
@tanattv/lyt.
Global npm installation and first-use managed binary downloads are side effects. Do not perform either without explicit user approval. Check capabilities with:
lyt doctor --json
Inspect before downloading. These commands have no download side effects:
lyt info --json "URL" # media metadata and formats (schema lyt.info.v1)
lyt capabilities --json # commands, flags, and schemas (lyt.capabilities.v1)
lyt info describes what a URL offers (title, duration, formats); lyt doctor
describes what the local environment can do. Use lyt capabilities to discover
the CLI surface instead of parsing human help text.
Always quote URLs. Prefer --dry-run --json before a large or uncertain job.
For bounded agent calls, --json emits one JSON document using schema lyt.result.v1 on stdout; setup and progress diagnostics go to stderr.
lyt --audio --dry-run --json "URL"
lyt --audio --json "URL"
lyt --mp3 -q 192K --json "URL"
lyt --video -q 1080p --max-filesize 2G --json "URL"
lyt --clip 1:10-2:45 --mp3 --json "URL"
lyt --list-formats --json "URL"
Files go to ./downloads under the current working directory unless -o is
supplied. Before a real job, confirm the intended output directory when it is
material to the user's workflow.
Keep these behaviors opt-in:
--playlist--force-overwrite--redownload- browser cookies or authentication material
- external downloaders
- managed tool installation
Never use cookies, tokens, private URLs, or authentication material unless the user explicitly requests it. Never include those values in logs or bug reports.
After success, read results[].files and report those exact paths. If a result
is skipped, explain whether a matching artifact already exists or a size guard
was triggered. Use --redownload only when the user asks for another copy.
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 First seen · 66 lines · 46 tokens per session scan A 01e7ac4087c9
lyt is a skill published in the GitHub repository TanaTTV/lyt (1 stars, last pushed 23d ago), licensed MIT. It adds 46 tokens to every session and 588 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-31.
Other skills, from other repositories
qiaomu-cut
把一句话需求转成可复现、可验收视频工程的乔木智能剪辑导演。Use when the user asks to create, plan, edit, remix, explain, narrate, subtitle, animate, composite, or render a video; build English-learning movie mixes, person profiles, explainers, product launch videos, cinematic shorts, social clips, course/PPT videos, AI…
authoring-video-templates
Use when creating or editing a video template JSON (the template descriptor), adding or changing sections/filters/maps/variables/transitions/looks/motion/audio/layers, or debugging template validation errors in ffmpeg-video-composer.
core-architecture-patterns
Use when adding a segment type, platform adapter, editor manager, core service, or descriptor effect (look/grade/motion/section-audio field) in packages/ffmpeg-video-composer, or when wiring new dependencies into the tsyringe container.
ondevice-ffmpeg-engine
Use when building, modifying, or consuming the on-device FFmpeg engine — the Rust crate packages/ffmpeg-engine, the leclap-ffmpeg Expo native module, the run/probe/version/cancel API, the uniffi bindings, build-engine.sh, or the FFmpeg-from-source toolchain in scripts/ffmpeg.
cross-platform-ffmpeg
Use when working with FFmpeg across Node/Static/WASM, the PlatformBridge, the FFmpeg detection/fallback chain, or browser/React Native runtime constraints in ffmpeg-video-composer.
monorepo-dev-workflow
Use when building, testing, linting, formatting, typechecking, or running any app or package in the ffmpeg-video-composer monorepo, or when looking for the right pnpm/vp command.