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 totvs/engpro-advpl-tlpp-skills --skill tir-test-generatorgit clone --depth 1 https://github.com/totvs/engpro-advpl-tlpp-skillsWrote 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/totvs/engpro-advpl-tlpp-skills/tir-test-generator)<a href="https://agentmods.dev/skills/totvs/engpro-advpl-tlpp-skills/tir-test-generator"><img src="https://agentmods.dev/badge/skills/totvs/engpro-advpl-tlpp-skills/tir-test-generator/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/totvs/engpro-advpl-tlpp-skills/tir-test-generator"><img src="https://agentmods.dev/badge/skills/totvs/engpro-advpl-tlpp-skills/tir-test-generator.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.00110 | $0.07970 |
| Opus 5.5 | $0.00044 | $0.03188 |
| Sonnet 5.5 | $0.00022 | $0.01594 |
| Haiku 4.5 | $0.00011 | $0.00797 |
Grade A, and why
tir-test-generator 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 8d 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 — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protheus TIR Test Generator
Overview
Generate end-to-end interface test scripts in Python for the TOTVS Protheus ERP using the TIR (TOTVS Interface Robot) framework. TIR automates Protheus screens through the SmartClient/Webapp interface, validating complete user workflows including screen navigation, field interaction, grid manipulation, button clicks, and result assertions.
TIR tests use Python's unittest framework combined with the tir.Webapp class to:
- Connect to a running Protheus Webapp environment
- Navigate to specific routines via
Program() - Interact with screen elements (fields, grids, buttons, folders)
- Assert field values, screen states, and data integrity
- Tear down the session cleanly
When to Use
Use this skill when:
- Creating end-to-end UI tests for Protheus screens (CRUD, workflows)
- Testing MVC-generated screens via the SmartClient/Webapp interface → use
Webappclass - Testing SmartX / PO-UI screens (native Smart X routines) → use
Pouiclass - Validating critical user journeys (complete business flows)
- Testing screen navigation, menu access, and dialog handling
- Validating field interactions (fill, check, read values)
- Testing grid operations (add rows, edit cells, scroll, select)
- Validating reports via parameter screens
- Needing visual/interface-level regression tests
When NOT to Use
- Non-interface/business logic tests → Use the AdvPR skills (
advpr-mvc-script,advpr-execauto-script,advpr-api-script,advpr-smartview-script) - TLPP unit tests → Use ProBat (@TestFixture)
Webapp vs Poui — Which Class to Use?
| Routine type | TIR class | Import |
|---|---|---|
Legacy MVC (ModelDef/ViewDef/MenuDef) |
Webapp |
from tir import Webapp |
Legacy Browse (MBrowse, AxCadastro) |
Webapp |
from tir import Webapp |
SmartX native (totvs.framework.structure) |
Poui |
from tir import Poui |
| Mixed (SmartX UI + legacy ExecAuto) | Poui for UI tests |
from tir import Poui |
What ships with it
3 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.
- 8d ago Changed · +199 lines bab2c5f98cfd
- 1mo ago First seen · 399 lines · 110 tokens per session scan A 8c64e8bd7afb
tir-test-generator is a skill published in the GitHub repository totvs/engpro-advpl-tlpp-skills (164 stars, last pushed 8d ago), licensed MIT. It adds 110 tokens to every session and 7,970 once invoked, about $0.0004 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
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.