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 Czarnak/totally-integrated-claude --skill tia-doctorgit clone --depth 1 https://github.com/Czarnak/totally-integrated-claudeWrote 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/czarnak/totally-integrated-claude/tia-doctor)<a href="https://agentmods.dev/skills/czarnak/totally-integrated-claude/tia-doctor"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-doctor/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/czarnak/totally-integrated-claude/tia-doctor"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00558 |
| Opus 5 | $0.00018 | $0.00279 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
tia-doctor 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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tia-doctor
Use this skill only when the user explicitly asks to diagnose, verify, or debug the local TIA Portal automation environment.
Run
Full probe:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills\tia-doctor\probe.ps1 -RequiredMajorVersion 21
V21 C# Openness core only (the audit mode while Python and MCP are intentionally out of scope):
powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills\tia-doctor\probe.ps1 -RequiredMajorVersion 21 -SkipPython -SkipMcp
Add -Json to either command for machine-readable output.
Interpret results
pass: the scoped prerequisite is present and usable by the static probe.warn: an optional probe could not be completed or a non-required item is missing.fail: a required prerequisite for the requested scope is missing or unusable.
Report missing items using the probe's remediation text. Do not invent an installation command when the result already supplies one.
V21 checks
The core probe verifies:
- the exact TIA Portal V21 executable under a common Siemens installation path;
- the V21 modular Public API path (
PublicAPI\V21\net48); - the required modular core
Siemens.Engineering.Base.dll, plus file/assembly version evidence and the installed optionalSiemens.Engineering.*modules; - current Windows-user membership in the
Siemens TIA Opennesslocal group.
Registry entries are supplemental evidence only; they do not replace the exact Portal executable or modular core assembly checks.
Unless skipped, the full probe also checks:
siemens_tia_scriptingimportability throughpyorpython;tia-mcponPATHor aTiaMcpServerdotnet global tool.
Python and MCP are client/tooling choices, not prerequisites for direct C# Openness. Use the skip switches whenever those integrations are outside scope.
Safety and evidence boundary
The probe is read-only. It must not open TIA Portal, create projects, load an Openness assembly into the current process, modify registry keys or groups, install tools, or change user configuration. Static presence, version metadata, and group membership do not prove that a project can be opened or that a credentialed/live operation will succeed.
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.
- 12d ago First seen · 66 lines · 36 tokens per session scan A 26a81cb9ddc0
tia-doctor is a skill published in the GitHub repository Czarnak/totally-integrated-claude (57 stars, last pushed 27d ago), licensed MIT. It adds 36 tokens to every session and 558 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
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
phx-investigate
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Amp subagents only when useful.