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.00033 | $0.00525 |
| Opus 5.5 | $0.00013 | $0.00210 |
| Sonnet 5.5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 23d 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 — 64 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 is intentionally out of scope):
powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills\tia-doctor\probe.ps1 -RequiredMajorVersion 21 -SkipPython
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_scripting
importability through py or python.
Python is a client/tooling choice, not a prerequisite for direct C# Openness.
Use -SkipPython whenever that integration is 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.
- 23d ago Changed · -2 lines · -3 tokens per session 40a713d91d7a
- 1mo 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 (75 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 525 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
shiny-py-optimize
Diagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to…
shiny-r-optimize
Diagnose and fix performance problems in Shiny for R apps — slow startup, sluggish interactions, long-running blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny app is slow, hangs, recomputes too much, times out, or needs to support more users; when the user asks to…
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
endpoint-management
Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.