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-import-exportgit 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-import-export)<a href="https://agentmods.dev/skills/czarnak/totally-integrated-claude/tia-import-export"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-import-export/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-import-export"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-import-export.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.00017 | $0.00724 |
| Opus 5 | $0.00009 | $0.00362 |
| Sonnet 5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
tia-import-export 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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tia-import-export
Scope
Import/export strategy and round-trip design — full C# Openness implementation.
When the roadmap routes here, the entire solution is C#. Do not mix with Python wrapper calls.
Use this skill for
- choosing direct object edits vs import/export
- XML / SimaticML / AML / CAx strategy
- bulk engineering changes
- export granularity
- folder-structure planning
- overwrite behavior
- project / HMI / PLC / library round-trip workflows
- object-specific import/export compositions
- mixed import + low-level object-model editing
Execution pattern
- identify target object class and Openness composition
- identify exchange format (SimaticML, AML, XML)
- decide file-based vs direct-edit approach
- treat every import file as untrusted input: resolve the exact path, verify its provenance and expected object kind, and validate the format before opening the project for modification
- obtain explicit authorization for the exact project, target composition, overwrite policy, and intended import; an earlier export, compile, or static check is not authorization to mutate a live project
- define source root / target root / overwrite / structure; do not use
ImportOptions.Overrideas a default - use Openness import/export services on the correct composition and inspect any returned result object, messages, error count, and state
- compile relevant hardware/software after import and validate consistency state
- Do not save the project when import, result validation, or compile/consistency validation fails; close or roll back through the operation-specific supported mechanism
Exports can overwrite filesystem content even though they do not mutate the project. Resolve the output path and require an explicit overwrite decision before replacing an existing file.
Reference files
Load ONLY the reference file(s) relevant to the task. Do not load all files at once.
| Reference file | Load when the task involves |
|---|---|
references/overview.md |
general import/export principles, ExportOptions/ImportOptions enums, open references, SIMATIC ML versioning, exportable object matrix |
references/hmi-screens.md |
exporting or importing HMI screens, screen templates, pop-up screens, slide-in screens, permanent areas, faceplate instances |
references/hmi-tags-and-data.md |
HMI tag tables, individual HMI tags, cycles, connections, text lists, graphic lists, VB scripts, special HMI tag considerations (integrated connection, UDT) |
references/plc-blocks.md |
PLC block export/import (FB, FC, OB, DB), UDTs, know-how protection, failsafe blocks, system blocks, GRAPH, snapshots, instance DB creation, DB value access, OPC UA XML export, document export/import, open-reference and structural-change import |
references/plc-alarms-and-tags.md |
PLC tag tables, individual PLC tags/constants, alarm classes, PLC alarm text lists (XLSX), ProDiag supervisions, watch tables, force tables |
references/hardware-aml.md |
CAx/AML export and import, CaxProvider service, project-level vs device-level transfer, CaxImportOptions, TransferResult, type identifiers, AML structure |
references/project-data.md |
project-level texts export/import (XLSX), project graphics export/import |
What ships with it
8 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.
- 11d ago First seen · 56 lines · 17 tokens per session scan A 464606dc29f6
tia-import-export is a skill published in the GitHub repository Czarnak/totally-integrated-claude (57 stars, last pushed 25d ago), licensed MIT. It adds 17 tokens to every session and 724 once invoked, about $0.0001 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.…