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-multiusergit 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-multiuser)<a href="https://agentmods.dev/skills/czarnak/totally-integrated-claude/tia-multiuser"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-multiuser/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-multiuser"><img src="https://agentmods.dev/badge/skills/czarnak/totally-integrated-claude/tia-multiuser.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.00027 | $0.00531 |
| Opus 5.5 | $0.00011 | $0.00212 |
| Sonnet 5.5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
tia-multiuser 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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TIA Portal Multiuser Engineering
Scope
Multiuser Engineering workflows using the TIA Portal Openness API. Covers Local Sessions, Server Projects, and Multiuser Commissioning.
Reference files
Load ONLY the reference file(s) relevant to the task.
| Reference file | Load when the task involves |
|---|---|
references/v21-api-surface.md |
Comprehensive installed surface for Siemens.Engineering.Multiuser types. |
references/workflows-and-safety.md |
Exact V21 roots, project-server/session workflows, marking, locking, save/close/commit semantics, and remote-write gates. |
Key Workflows
Managing Local Sessions
- Resolve a project-server connection from
tiaPortal.ProjectServersby exact alias. - Resolve the exact
ServerProjectInforeturned byProjectServer.GetServerProjects(). - Create a
LocalSessionInfo, then open it throughtiaPortal.LocalSessions. - Use
LocalSession.Save(),Close(),IsUptoDate(),MarkingService, and—only for a supported server/exclusive session—CloseAndCommit(comment).
Use only the direct compositions and the session methods listed here. Do not translate UI terms into an intermediate service, conflict-options object, or parameterless check-in/update calls.
Project-server root
ProjectServerComposition servers = tiaPortal.ProjectServers;
LocalSessionComposition sessions = tiaPortal.LocalSessions;
Enforcement
- Require explicit remote-write authorization before creating/deleting a connection or session, adding a project, changing host/protocol/port, saving, closing with discard, or committing a server revision.
- Resolve server alias, project, group, session ID/path, and intended mode exactly; never select
.First()or[0]. - Check server lock state, session freshness, markings/conflicts, active users, and path/version prerequisites before mutation.
- Active monitoring or forcing jobs must be stopped before check-in/update workflows; non-markable edits can be lost in commissioning workflows.
Close()discards pending changes.CloseAndCommit()performs a remote commit and returns the created revision; neither is cleanup to call unconditionally.- Do not save or commit unless explicitly requested. Do not claim remote success without reading the returned revision/current server state.
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.
- 1mo ago First seen · 55 lines · 27 tokens per session scan A 91625328b138
tia-multiuser is a skill published in the GitHub repository Czarnak/totally-integrated-claude (75 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 531 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
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
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…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
head-of-pmo
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…