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-simatic-drivesgit 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-simatic-drives)<a href="https://agentmods.dev/skills/czarnak/totally-integrated-claude/tia-simatic-drives"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-simatic-drives/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-simatic-drives"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-simatic-drives.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.00058 | $0.00741 |
| Opus 5 | $0.00029 | $0.00370 |
| Sonnet 5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
tia-simatic-drives 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 13d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tia-simatic-drives
Scope
Startdrive and drive-specific engineering — full C# Openness implementation.
When the roadmap routes here, the entire solution is C#.
Do not mix with Python wrapper calls.
Always load tia-csharp-common first (done by roadmap).
Reference files
| Reference file | Load when the task involves |
|---|---|
references/drives-overview.md |
Core patterns for Startdrive/SINAMICS engineering (Navigate, Parameters, Telegrams, DFI, Safety, Security) |
references/motion-control.md |
Detailed reference for Siemens.Engineering.MC namespaces (Drives, DFI, SecurityObjects, Enums) |
references/download.md |
Startdrive-specific and common Download/Upload check configurations |
references/api-catalogue.md |
Complete inventory of all 64 public types in the installed V21 Startdrive module |
Execution pattern
- Confirm the task is drive-specific (Startdrive, SINAMICS, drive controller, PROFIdrive)
- Read
references/drives-overview.md - Resolve the drive device and drive object using exact selectors; recursively traverse nested device items and fail on zero or ambiguous matches
- Get
DriveObjectContainerviaGetService<>()on the device item to accessDriveObjects - Use
DriveObject.Parametersfor parameter access,.Telegramsfor telegram find/insert/erase/size operations - Use
GetService<DriveFunctionInterface>()for commissioning, motor/encoder config, DFI, and drive-object activation/type handling - For download/upload handling, include Startdrive-specific check configurations from
Siemens.Engineering.Download.ConfigurationsandSiemens.Engineering.Upload.Configurations - For network/PROFIdrive timing — see
tia-networks/references/subnets-and-nodes.md
Safety boundary
- Require explicit live-operation authorization for online parameter writes, download/upload, factory reset, RAM-to-ROM copy, drive encryption/UMAC changes, and Safety commissioning.
- Require explicit mutation authorization for offline parameters, telegrams, drive-object type/activation, motor/encoder projection, Technology Extension install/uninstall, and report overwrite.
- Bind exact selectors to the project, device, nested
DeviceItem, drive-object number, parameter name/number/index, telegram type, and requested value. Never use.First(),[0], or catalog-order assumptions. - Inventory current parameters, telegrams, topology, safety/security state, Technology Extensions, and dependent PLC/HMI configuration before mutation. Factory reset, encryption deactivation, forced package removal, and telegram deletion are destructive.
- Inspect every boolean result and every download/upload configuration. Unknown or unsupported configurations fail closed; never approve all checks automatically.
- Secrets must arrive as
SecureStringfrom the caller's approved secret source. Never embed, print, persist, or reconstruct passwords in examples. - Do not save: call
project.Save()only when persistence was explicitly requested and post-change verification succeeded. - Static API checks are not commissioning evidence. Online state, firmware/device support, Safety acceptance, and successful drive behavior require an authorized live V21 test.
What ships with it
4 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.
- 13d ago First seen · 54 lines · 58 tokens per session scan A 3d71ba05f93a
tia-simatic-drives is a skill published in the GitHub repository Czarnak/totally-integrated-claude (57 stars, last pushed 27d ago), licensed MIT. It adds 58 tokens to every session and 741 once invoked, about $0.0003 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
bootstrap-solution
Bootstrap or guide a reproducible .NET solution with explicit F# or C# language choice, SDK selection, project layout, test project setup, and initial validation commands.
build-csharp-project
Build or modify idiomatic C# .NET projects using nullable-aware APIs, records/classes, async/task behavior, analyzer conventions, tests, and repo-local validation.
csharp-developer
Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor…
dotnet-core-expert
Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
cran-extrachecks
Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback.…