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-reviewgit 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-review)<a href="https://agentmods.dev/skills/renanlido/tia-harness/tia-review"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/tia-review/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-review"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/tia-review.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.00190 | $0.04681 |
| Opus 5.5 | $0.00076 | $0.01872 |
| Sonnet 5.5 | $0.00038 | $0.00936 |
| Haiku 4.5 | $0.00019 | $0.00468 |
Grade A, and why
tia-review 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tia-review — audit an existing project vs the baseline (class R, read-only)
Audit a connected TIA project against the non-negotiable baseline (TIA
best-practices §0) and the naming/architecture rules (§4/§5/§8). It is a
read-only review: it enumerates the project model through the tia MCP read tools and
reports deviations — it never changes anything.
Besides the baseline findings it reports, as information only, the objects of each CLP that
nothing references (unused-object candidates, from the cross-references): a separate
Unused objects section, never a baseline rule.
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_crossrefs(step 5): a409crossrefs_unavailableanswer (quote itserror,kindandhint, report theUnused objectssection as not done, and finish the rest of the review); a409cursor_staleanswer, orcoveragecounts that differ 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 review as above. - For the
status:"running"andkind:"busy"answers oftia_crossrefs, step 5 says which job to poll and what to do next; the bullet above applies to every other call.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +133 lines · +15 tokens per session 9c4f67ed1dde
- 10d ago First seen · 92 lines · 175 tokens per session scan A cf306fe17fbd
tia-review is a skill published in the GitHub repository renanlido/tia-harness (11 stars, last pushed 4d ago), licensed MIT. It adds 190 tokens to every session and 4,681 once invoked, about $0.0008 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.
kicad-pcb-review
Use this skill when reviewing, fixing, validating, or preparing KiCad PCB projects with the kicad MCP server.
kicad-pcb-review
KiCad PCB review and manufacturing readiness agent skill for Cursor.
rtl-review
Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.
vllm-rocm-pr-review
Review AMD/ROCm-related pull requests from the vllm-project/vllm GitHub repository and produce a single combined Chinese report: a detailed PR summary (summary, background & motivation, code-change analysis with Mermaid diagrams, technical principles, discussion highlights, risk table) followed by severity-sorted…
arch-review
Read-only architecture review of RTL vs uArch spec with area/timing/power tradeoffs. Use for post-RTL architecture sign-off or suspected spec mismatch.