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.
git clone --depth 1 https://github.com/y49/tliveWrote 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/commands/y49/tlive/status)<a href="https://agentmods.dev/commands/y49/tlive/status"><img src="https://agentmods.dev/badge/commands/y49/tlive/status/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/commands/y49/tlive/status"><img src="https://agentmods.dev/badge/commands/y49/tlive/status.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.00012 | $0.00222 |
| Opus 5.5 | $0.00005 | $0.00089 |
| Sonnet 5.5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
status 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.
What it actually says
Run tlive status and show the output to the user verbatim. If the mode:
line says notify (the default), point out that remote approval is off — tlive
only watches + notifies, and tool prompts stay local; enable phone Allow/Deny
with tlive mode full. full means remote approval is on for the main
session; all means sub-agent approvals are held too (no terminal dialog for
a held one until the window ends — only worth it when nobody is at the
keyboard); off disables tlive entirely. If the Codex line says degraded or
off, explain: Codex
approvals are local-only right now (the native prompt still works; nothing is
ever auto-run) — off usually means codex is not on PATH, degraded means the
app-server child keeps failing (see ~/.tlive/codex-appserver.log).
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 First seen · 16 lines · 12 tokens per session scan A 83e59562ea23
status is a command published in the GitHub repository y49/tlive (215 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 222 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
designmatch
Bootstrap the designmatch skill in a React Native project from a Claude Design link. Auto-imports the Visual QA stub helper (visual-qa.ts), writes default state.vqa.json, registers the canonical source, updates .gitignore, and prints the wiring snippet. Use when starting visual-parity work on a new RN screen or when…
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
create-plugin
Guided end-to-end plugin creation workflow with component design, implementation, and validation.