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 renanlido/tia-harness --skill tia-verifygit clone --depth 1 https://github.com/renanlido/tia-harnessWrote 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/renanlido/tia-harness/tia-verify)<a href="https://agentmods.dev/skills/renanlido/tia-harness/tia-verify"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/tia-verify/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/renanlido/tia-harness/tia-verify"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/tia-verify.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.00242 | $0.05408 |
| Opus 5.5 | $0.00097 | $0.02163 |
| Sonnet 5.5 | $0.00048 | $0.01082 |
| Haiku 4.5 | $0.00024 | $0.00541 |
Grade A, and why
tia-verify 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 7d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tia-verify — the verification ladder, rungs 0–3, and the FAT/SAT I/O list, rung 6 (class M-off)
Prove a project "works in practice" offline, the only honest pre-deploy evidence (the style/architecture
audit is tia-review). The ladder: rung 0 static (spec-validate), rung 1 compile + consistency,
rung 2 project-as-code export + COMPARE (roundtrip proof), rung 3 simulation (PLCSIM, future). A
clean compile is the precondition (Gd9) for export and download — so this gate-keeps tia-handoff.
Rung 6 is the FAT/SAT delivery: this skill covers its I/O list (step 6), generated from tia_io_map, a
read independent of the compile; the human signs the FAT/SAT record, the skill never does.
Errors and reporting
- First call
tia_ping: continue only if it reportsreachable:trueandactivated:true.activated:nullwith a busydetailmeans a job is still running: polltia_job_statuswith thejobIdyou hold, or wait and ping again. Otherwise stop, quote itsdetailandhintverbatim and say that nothing was changed (prerequisites:tia_guide {"topic":"gotchas"}). - If no
tia_*tool is available, thetiaMCP is not connected: say so and stop. Never continue from memory and never work around it with hand-made HTTP calls (they bypass the MCP's gate checks). - On a tool error (
isError:true), quote itserrorandkindverbatim, relay itshint, and state what was done and what was not. Apply only the remedy the hint or this skill names, at most once; otherwise stop and ask. - Never report success after an error, never retry a refused call with changed arguments, and never cross a human gate: relay a
requires_human_actionanswer verbatim and wait for the human. status:"running"orkind:"busy"is not a failure: polltia_job_status {jobId}. After atimeout, check the state before repeating anything.- This skill names these remedies for
tia_io_map(step 6): a409cursor_staleanswer, orcoveragethat differs between pages (restart the page walk from the first page, once for each); and a page that arrives with an omission marker (repeat that page with a smallerlimit, at most three times). Every other tool error stops the I/O list as above: report it as NOT complete, or as not done when no page was read. - For the
status:"running"andkind:"busy"answers oftia_io_map, step 6 says which job to poll and what to do next; the bullet above applies to every other call.
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.
- 7d ago Changed · +122 lines · +50 tokens per session 170a32f03164
- 10d ago First seen · 111 lines · 192 tokens per session scan A 04bd009c2926
tia-verify is a skill published in the GitHub repository renanlido/tia-harness (11 stars, last pushed 4d ago), licensed MIT. It adds 242 tokens to every session and 5,408 once invoked, about $0.0010 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-10-18.
Other skills, from other repositories
tiaportal-mcp
A skill for controlling Siemens TIA Portal, the engineering software used to configure Siemens PLCs and HMIs. It works through an MCP server, a tool connection that lets an agent inspect and change projects.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
passport-build
Validate and package FoloToy AI Passport firmware, including a verified merged image and matching debugging artifacts. Use for build, test, and firmware-package requests; does not flash, commit, or publish.
passport-device-test
Guide authorized flashing and on-device acceptance of FoloToy AI Passport firmware, including device discovery and bounded serial observation. Use for explicit device-test or flash requests, not merely because a build succeeded.