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 24373054/TLAH-Studio --skill update-configgit clone --depth 1 https://github.com/24373054/TLAH-StudioWrote 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/24373054/tlah-studio/update-config)<a href="https://agentmods.dev/skills/24373054/tlah-studio/update-config"><img src="https://agentmods.dev/badge/skills/24373054/tlah-studio/update-config/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/24373054/tlah-studio/update-config"><img src="https://agentmods.dev/badge/skills/24373054/tlah-studio/update-config.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.00032 | $0.00386 |
| Opus 5 | $0.00016 | $0.00193 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
update-config 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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 48 lines · 32 tokens per session scan A 9d656fdf0661
update-config is a skill published in the GitHub repository 24373054/TLAH-Studio (5 stars, last pushed 25d ago), with no licence file. It adds 32 tokens to every session and 386 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
frontend-dev
Build or update UI screens, dashboards, forms, modals, and tables. Use when the subtask is primarily a frontend implementation — page layout, component composition, responsive design, interaction polish, or UI state wiring to existing APIs.
write-tech-spec
Draft a technical specification under specs/ /TECH.md before writing code. Use when the user asks for a "spec", "tech spec", or "implementation plan" — or when a task is large enough that getting the approach reviewed before coding is cheaper than writing the code twice.
implement-specs
Implement code changes from an existing specs/ /TECH.md, one Implementation Plan step per commit, and update the spec in the same PR whenever reality diverges. Use after write-tech-spec, or when the user points at an existing TECH.md and says "implement this".
ui-design-system
Polish existing UI to production quality — spacing, typography, color consistency, hover/focus states, responsive breakpoints. Use when the subtask is about visual polish, design-system enforcement, or beautifying an existing screen rather than building new features.
verify
Verify recent code changes work end-to-end by building, running tests, and exercising affected features. Use when the user asks to verify changes, requests "/verify", or wants confirmation a feature actually works.
spec-driven-implementation
Orchestrate the full spec-then-build workflow for a non-trivial task — write a tech spec, get review, then implement step-by-step keeping spec and code in sync. Use when the user asks to "spec-drive this", "do this properly with a spec", or wants the full Warp-style discipline.