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.handoffgit 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.handoff)<a href="https://agentmods.dev/skills/renanlido/tia-harness/tia.handoff"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/tia.handoff/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.handoff"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/tia.handoff.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.00175 | $0.01299 |
| Opus 5 | $0.00088 | $0.00649 |
| Sonnet 5 | $0.00035 | $0.00260 |
| Haiku 4.5 | $0.00017 | $0.00130 |
Grade A, and why
tia.handoff 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 11d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tia.handoff — prepare the gate, let a human act (class GATE)
The harness is an assistant up to the gate, never an autonomous commissioner. Anything
that touches the physical controller, the network, secrets, or safety stops here: this
skill assembles the approval envelope (requires_human_action) — what can be done, what
the human must do, the plan + hash, and the exact resume call — and then stops.
When to use
- After
tia.verifyis clean and the user wants to download / deploy / go online / scan / commission. - Whenever a step needs a secret (master secret / UMAC) or touches F (safety).
The gates (and the tool that fronts each)
| Gate | Action | Tool | What the human must approve |
|---|---|---|---|
| G1 | open/connect project (1st time) | tia_connect (+ tia_show_ui) |
confirm the TIA trust dialog on the serve host |
| G3 | download (CPU STOP → overwrite → restart) | tia_download |
the load preview: StopAll, OverwriteSystemData, StartModule |
| G4 | go online (connect to live CPU) | tia_online |
it is safe to connect to the target machine |
| G7 | network scan (accessible devices) | tia_accessible_devices |
probing the local network via the PG/PC NIC |
| G6 | master secret / UMAC | tia_mastersecret_set, connect umac* |
supply the secret (human/credential vault) |
| G5 | safety/F author·modify·download | — | never autonomous; F deploy is a human, gated action |
Two classes of human interaction. The table above is approval gates — a human approves an action that touches the controller, network, secrets, or safety. There is a second class: GUI-config gates — a human clicks a setting that TIA does not expose via Openness (the OPC UA runtime license / server interface, PUT/GET, the first-connect trust dialog). Those surface during scaffold/verify — e.g. a compile error "OPC UA license is not sufficient" is a gate, not a bug. Don't retry them blindly; the exact GUI steps for each are in the harness guide (
codex/AGENTS.md→ "Human interaction points (GUI gates)").
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.
- 11d ago First seen · 75 lines · 175 tokens per session scan A e9f4d007b8df
tia.handoff is a skill published in the GitHub repository renanlido/tia-harness (5 stars, last pushed 1mo ago), licensed MIT. It adds 175 tokens to every session and 1,299 once invoked, about $0.0009 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
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.
solidworks-fillet-chamfer-cnc
A SolidWorks skill for creating CNC parts with multiple rounded edges and chamfers, which are angled or softened edges used in manufacturing. It includes parameter checks, edge selection, and evidence after rebuilding the model.
solidworks-threaded-holes
A SolidWorks skill for creating and checking ISO metric internal threaded holes, such as M6, in new parts. It covers supported blind and through holes, chamfers, thread direction, and delivery evidence.
solidworks-vibecad
A planning guide for turning natural-language mechanical design requests into structured, parameterized SolidWorks plans that can be reviewed before execution.
eide
A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.