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/ferroxlabs/tvcontrol/chart-analysisnpx skills add FerroxLabs/tvcontrol --skill chart-analysisgit clone --depth 1 https://github.com/FerroxLabs/tvcontrolWhat 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.00037 | $0.00579 |
| Opus 5 | $0.00018 | $0.00290 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
chart-analysis 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.
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.
- 2d ago First seen · 65 lines · 37 tokens per session scan A 980ed25a0529
chart-analysis is a skill published in the GitHub repository FerroxLabs/tvcontrol (37 stars, last pushed 5d ago), with no licence file. It adds 37 tokens to every session and 579 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
google-flow-generate
Generate images and video using a Google AI Pro subscription via Google Flow (labs.google/flow), driven by browser automation (the google-flow MCP server), to avoid paying per-credit services for what Google already covers. Use when the user asks to generate an image or video and no specific other service is named.…
web-debug-workflow
Use when Web Debug is explicitly requested or a local web bug needs browser-grounded evidence such as DOM, console, network, debugger, framework runtime, responsive geometry, replay, or fix verification. Do not use for exact unit, Go, or Vitest failures with no browser symptom; keep those on the native runner path.
manual-parity-qualification
Build traceable web qualification coverage from approved manual cases or source-backed product requirements using reviewed baselines, repository-native Playwright/API tests, coverage crosswalks, and run records. Use for manual-parity, multi-role journey, authorization-branch, and release-qualification requests; not…
architect-bridge-debug
Use this skill whenever you are debugging architect-tool's ChatGPT bridge, running live browser automation diagnostics, or using askchatgpt to consult another AI model during a debugging session. Triggers when: the user asks you to debug the bridge, asks you to "talk to GPT about this", asks you to use the tool to…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
building-product-empty-states
Guide for adding a product setup empty state — the skippable first-run screen a product scene shows until real data arrives, built on the shared ProductEmptyState component. Use when adding an empty state or first-run/setup screen to a product scene, declaring emptyState on a SceneExport, writing a product…