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 mumez/smalltalk-dev-plugin --skill st-testgit clone --depth 1 https://github.com/mumez/smalltalk-dev-pluginWrote 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/mumez/smalltalk-dev-plugin/st-test)<a href="https://agentmods.dev/skills/mumez/smalltalk-dev-plugin/st-test"><img src="https://agentmods.dev/badge/skills/mumez/smalltalk-dev-plugin/st-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.
<a href="https://agentmods.dev/skills/mumez/smalltalk-dev-plugin/st-test"><img src="https://agentmods.dev/badge/skills/mumez/smalltalk-dev-plugin/st-test.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.00040 | $0.00491 |
| Opus 5.5 | $0.00016 | $0.00196 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
st-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 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.
What it actually says
Run SUnit Tests
Execute SUnit tests after importing changes to the Smalltalk image.
Usage
/st-test TestClassName # run a single test class
/st-test PackageName-Tests # run all tests in a package
Steps
With arguments: run a specific test class or package
- Determine whether the argument is a class name or a package name
- Class name (e.g.
RsJsonTest) → callrun_class_test - Package name (e.g.
RediStick-Json-Tests) → callrun_package_test
- Class name (e.g.
- Report pass/fail counts and any failures
Without arguments: run all test packages in the project
When no arguments are given, discover and run all test packages automatically:
-
Locate the source directory — read
.projectfrom the repository root and extract thesrcDirectoryvalue. Resolve it to an absolute path. -
Identify test packages — find the
BaselineOfpackage inside the source directory (a directory starting withBaselineOf) and read itsBaselineOfXXX.class.st. Parse thebaseline: specmethod and collect all packages whose names end with-Tests(or follow the project's test-naming convention). -
Check what is already imported — call
list_packagesto get the list of packages currently loaded in the Smalltalk image. -
Run tests for imported packages — for each test package that is present in the image, call
run_package_testand report the pass/fail results. -
Report unimported packages — for any test package found in the BaselineOf but not loaded in the image, skip running tests and report it to the user with a note that they can run
/st-importfirst to load it.
Examples
/st-test RsJsonTest
/st-test RediStick-Json-Tests
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 · 47 lines · 40 tokens per session scan A 5eeae23a1e18
st-test is a skill published in the GitHub repository mumez/smalltalk-dev-plugin (15 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 491 once invoked, about $0.0002 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
flow-next-features
Seed or maintain the committed user-POV drive map at .flow/features/ so QA and drive reuse how a user reaches each feature.
flow-next-qa
Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qaverdict receipt.
maestro-work
The contract every playbook shares - the brief a writer receives, the rules it writes by, the handback it returns, and the store record the holder keeps. Reuse existing checks and add tests only for concrete uncovered behavior or risk.
modernize-test-starter
Modernize QUnit unit tests and OPA5 integration tests to the UI5 Test Starter concept. Use this skill when: The linter reports prefer-test-starter for .qunit.html or .qunit.js files Test HTML files use manual sap-ui-core.js bootstrapping instead of Test Starter's runTest.js/createSuite.js Test JS files use…
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.