A test runner for SUnit, the Smalltalk testing framework, connected to a running Pharo or Squeak programming environment.

Run one test class, all tests in a package, or automatically discovered test packages after code changes.

It lets you check whether imported code works without manually finding and running tests. It reports how many tests passed or failed and identifies failures.

st-test — Skill by mumez

Install

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.

agentmods

npx agentmods add skills/mumez/smalltalk-dev-plugin/st-test

Any agent

npx skills add mumez/smalltalk-dev-plugin --skill st-test

Clone the repo

git clone --depth 1 https://github.com/mumez/smalltalk-dev-plugin

Made for: Claude Code, Codex.

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 491 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00040	$0.00491
Opus 5	$0.00020	$0.00246
Sonnet 5	$0.00008	$0.00098
Haiku 4.5	$0.00004	$0.00049

Measured 2d ago against content hash 5eeae23a1e18, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

skills/st-test/SKILL.md · 47 lines

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) → call run_class_test
- Package name (e.g. RediStick-Json-Tests) → call run_package_test
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 .project from the repository root and extract the srcDirectory value. Resolve it to an absolute path.
Identify test packages — find the BaselineOf package inside the source directory (a directory starting with BaselineOf) and read its BaselineOfXXX.class.st. Parse the baseline: spec method and collect all packages whose names end with -Tests (or follow the project's test-naming convention).
Check what is already imported — call list_packages to 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_test and 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-import first to load it.

Examples

/st-test RsJsonTest
/st-test RediStick-Json-Tests

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.

2d ago First seen · 47 lines · 40 tokens per session scan A 5eeae23a1e18

Subscribe to this mod's changes

st-test is a skill published in the GitHub repository mumez/smalltalk-dev-plugin (15 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 491 once invoked, about $0.0002 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.

Testing claude-code marketplace mcp pharo-smalltalk plugin smalltalk

exec

Execute plan tasks sequentially using subagents. Use when user says 'exec', 'execute plan', 'run plan', or wants to implement a plan file task by task with isolated subagents.

umputun/cc-thingz · 41 tokens

pr

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

umputun/cc-thingz · 51 tokens

backlog

Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…

umputun/cc-thingz · 96 tokens

ask-codex

Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…

umputun/cc-thingz · 103 tokens

new

Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.

umputun/cc-thingz · 56 tokens

clarify

This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…

umputun/cc-thingz · 91 tokens