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 spec-validategit 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/spec-validate)<a href="https://agentmods.dev/skills/renanlido/tia-harness/spec-validate"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/spec-validate/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/spec-validate"><img src="https://agentmods.dev/badge/skills/renanlido/tia-harness/spec-validate.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.00172 | $0.01910 |
| Opus 5.5 | $0.00069 | $0.00764 |
| Sonnet 5.5 | $0.00034 | $0.00382 |
| Haiku 4.5 | $0.00017 | $0.00191 |
Grade A, and why
spec-validate 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-validate — deterministic project-spec validation (class R, rung 0)
Validate a structured TIA project-spec (the input model defined by the TIA
best-practices baseline §13.2) and report every violation by named rule. Ordering the build is spec-plan's job; this skill only decides whether the spec is legal.
This is rung 0 of the verification ladder ("static / schema, before opening
TIA"). It is class R: deterministic and read-only — no serve API, no TIA Portal.
Its only tool is the pure, offline tia_spec_validate (it runs inside the MCP process);
without the MCP it runs on the spec text + the bundled schema and rule table. It never
mutates anything and never crosses a gate.
Errors and reporting
- Needs no
serveand no TIA Portal: thetia_*tools named here are pure and offline, so do not calltia_ping. If they are not in the tool list, say so and use the fallback this skill names, or stop. - Report the tool's answer as returned (violations,
error,kind,hint) and state what was done and what was not. Never fix the input silently, never retry with changed input to get past a failure, and never report success after an error.
When to use
- The user pastes or points to a project-spec (JSON) and asks to validate/check/lint it.
- Before
cpu-selectis finalized into devices, or before any scaffold/creation step. - As a pre-flight any time a spec is edited, to catch errors that would otherwise only surface deep inside Openness.
Inputs
- A project-spec object (JSON) — inline, a file path, or pasted text.
- The bundled schema:
../../../schemas/project-spec.schema.json(Draft 2020-12,additionalProperties:false). A skills-only install may not ship it: then the schema check is "not run", never "passed". - The bundled rule reference:
RULES.md(the deterministic cross-field rules, each with a stable ID). - A bundled valid example to diff against intuition:
examples/line2.valid.json.
Outputs
What ships with it
2 files 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.
- 10d ago First seen · 117 lines · 172 tokens per session scan A 7d320d5950c6
spec-validate is a skill published in the GitHub repository renanlido/tia-harness (11 stars, last pushed 4d ago), licensed MIT. It adds 172 tokens to every session and 1,910 once invoked, about $0.0007 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.
iaiops-factory
Factory edition of iaiops — discrete-manufacturing lines: OPC-UA, Modbus-TCP/RTU, Siemens S7comm (S7-300/400/1200/1500), Mitsubishi MC/MELSEC, Omron FINS (CS/CJ/CP/NX), Allen-Bradley EtherNet/IP (ControlLogix/CompactLogix), EtherCAT (CoE/SOEM), PROFINET (DCP discovery), MTConnect (CNC machine tools), IO-Link (master…
gx3-existing-project-audit
Analyze an existing Mitsubishi GX Works3 .gx3 project with gx3-cli when the user asks what a ladder does, why a device turns on, or whether a project has risks.
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…