advpl-specialist: Command for Claude Code

.cursor/commands/test.md

test is a command for Claude Code, Cursor from thalysjuvenal/advpl-specialist. It costs 0 tokens per session (539 once invoked), scanned A, original, MIT.

A command for generating ProBat unit tests for TLPP code in the TOTVS Protheus system. Unit tests check individual functions or methods against expected results.

In plain words
What is it for?
Reading a TLPP source file, identifying normal and edge cases, and generating unit or API test files. ProBat requires TLPP files.
Why use it?
It helps create tests for TLPP code without drafting every test file by hand.

Command for Claude CodeCursor

Written for Claude Code and Cursor: shipped in a Claude Code plugin, but also installed under .cursor/.

This is thalysjuvenal/advpl-specialist's own configuration. It tells Claude Code and Cursor how to work on advpl-specialist itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything advpl-specialist configures →

Part of the advpl-specialist plugin — 18 skills, 14 commands, 2 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to thalysjuvenal/advpl-specialist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/thalysjuvenal/advpl-specialist/main/.cursor/commands/test.md
Clone the repo
git clone --depth 1 https://github.com/thalysjuvenal/advpl-specialist

Made for: Claude Code, Cursor.

Or install advpl-specialist, the plugin that ships this one along with the rest of its 18 skills, 14 commands, 2 hooks.

Wrote 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.

agentmods badge for test

README.md
[![agentmods](https://agentmods.dev/badge/commands/thalysjuvenal/advpl-specialist/test/github.svg)](https://agentmods.dev/commands/thalysjuvenal/advpl-specialist/test)
Your own site
<a href="https://agentmods.dev/commands/thalysjuvenal/advpl-specialist/test"><img src="https://agentmods.dev/badge/commands/thalysjuvenal/advpl-specialist/test/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.

agentmods 80×15 button for test

Your own site · 80×15
<a href="https://agentmods.dev/commands/thalysjuvenal/advpl-specialist/test"><img src="https://agentmods.dev/badge/commands/thalysjuvenal/advpl-specialist/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 539 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00539
Opus 5 $0.00000 $0.00269
Sonnet 5 $0.00000 $0.00108
Haiku 4.5 $0.00000 $0.00054

Measured 9d ago against content hash 49a8f2226f6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

test 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 9d 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.

.cursor/commands/test.md · 31 lines

How it starts

The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/test — Generate ProBat unit tests for TLPP classes and functions

You are an expert ADVPL/TLPP assistant for TOTVS Protheus. This command generates ProBat unit tests for TLPP code.

Knowledge to load first

Locate the advpl-specialist skills (installed via npx skills add thalysjuvenal/advpl-specialist; in this repository they live under skills/) and read, in order:

  1. skills/probat-testing/reference.md
  2. skills/probat-testing/patterns-unit-tests.md

Important: ProBat is TLPP only

ProBat only works with .tlpp files. If the target is a .prw file, tell the user that ProBat requires TLPP and suggest running the migrate command first to convert the source to TLPP. The generated test file itself is always .tlpp, even when testing ADVPL functions.

Workflow

  1. Parse the target file/function, --type (unit or api, default unit), and other flags (--output, --suite, --owner).
  2. Read the target source to understand what needs to be tested.
  3. Identify test cases: functions/methods to test, input parameters and expected outputs, edge cases (NIL values, empty strings, invalid types, boundary values), and error scenarios.
  4. Draft a plan: test file name/path, test class/function name, list of test methods with descriptions, assertions to use, and Setup/TearDown needs. Present it and wait for approval.
  5. After approval, generate the .tlpp test file following ProBat conventions.
  6. Report what was created and how to run the tests.

Output rules

  • #include "tlpp-probat.th" (and tlpp-core.th if needed).
  • Declare a proper namespace: test.<module> or custom.tests.<module>.
  • Use @TestFixture with owner and target properties.
  • Use @Test with descriptive mandatory descriptions.
  • Use typed local variable declarations and appropriate assertions (assertEquals, assertTrue, etc.).
  • Add @OneTimeSetUp, @Setup, @TearDown, @OneTimeTearDown methods when needed.
  • All test functions/methods must return .T..
  • For --type api, use tlpp.rest.runTestSimple to exercise the REST endpoint.
  • Compilation must be validated in TDS / VS Code TOTVS extension — never claim the code compiles.

Read the full file on GitHub · 31 lines

Changes

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.

  1. 9d ago First seen · 31 lines · 0 tokens per session scan A 49a8f2226f6e

Subscribe to this mod's changes

test is a command published in the GitHub repository thalysjuvenal/advpl-specialist (186 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 539 tokens. 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.