st-eval

A skill for evaluating Smalltalk expressions in a running Pharo or Squeak image, which is Smalltalk's live development environment. It also describes safe ways to inspect results, object state, errors, and blocking operations.

In plain words
What is it for?
Use it to run Smalltalk expressions, verify object values, inspect intermediate results, debug behavior, and check whether the Smalltalk image is connected.
Why use it?
It lets the agent check and debug Smalltalk code incrementally while connected to the live program state.

Skill for Claude CodeCodex

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-eval
Any agent
npx skills add mumez/smalltalk-dev-plugin --skill st-eval
Clone the repo
git clone --depth 1 https://github.com/mumez/smalltalk-dev-plugin

Made for: Claude Code, Codex.

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 691 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.

ModelPer sessionOnce invoked
Fable 5 $0.00049 $0.00691
Opus 5 $0.00024 $0.00345
Sonnet 5 $0.00010 $0.00138
Haiku 4.5 $0.00005 $0.00069

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

Security

Grade A, and why

st-eval 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-eval/SKILL.md · 94 lines

How it starts

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

Execute Smalltalk Code

Evaluate arbitrary Smalltalk expressions in the running Smalltalk image via mcp__smalltalk-interop__eval.

Essential Rules

Always use printString — MCP returns serialized output. Raw objects cause errors or unreadable results:

✅ MyClass new doSomething printString
✅ collection printString
❌ MyClass new doSomething

Wrap risky code in on:do: — Uncaught errors in eval crash the MCP call with no useful message:

| result |
result := Array new: 2.
[ result at: 1 put: (riskyOperation) printString ]
  on: Error do: [:ex | result at: 2 put: ex description].
^ result

Use fork for blocking operations — Code that opens a dialog or blocks the image will cause the MCP call to hang indefinitely. Detach it:

[ <blocking expression> ] fork.
^ 'started'

Common Patterns

Connection check

Smalltalk version

Inspect intermediate values

| step1 step2 |
step1 := objA computeStep1.
step2 := step1 processStep2.
^ { 'step1' -> step1 printString. 'step2' -> step2 printString } asDictionary printString

Inspect object state

{
  'class' -> obj class name.
  'value' -> obj printString.
  'size'  -> obj size printString
} asDictionary printString

Safe collection access

collection ifEmpty: ['empty'] ifNotEmpty: [:col | col first printString]

Error-capturing eval

| result |
result := Array new: 2.
[
  | obj |
  obj := MyClass new name: 'Test'.
  result at: 1 put: obj process printString.
] on: Error do: [:ex |
  result at: 2 put: ex description
].
^ result

Troubleshooting

Symptom Cause Fix
MCP call hangs / no response Blocking operation (dialog, modal, infinite loop) Wrap in fork
Error: cannot serialize Returning raw object Add printString
Debugger window opened in the Smalltalk image Uncaught error triggered the debugger Close debugger in the Smalltalk image, then re-eval with on:do:
MessageNotUnderstood Method doesn't exist or typo Check with mcp__smalltalk-interop__search_implementors

Read the full file on GitHub · 94 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. 2d ago First seen · 94 lines · 49 tokens per session scan A a420a922461d

Subscribe to this mod's changes

st-eval is a skill published in the GitHub repository mumez/smalltalk-dev-plugin (15 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 691 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.

Related

Other skills, from other repositories

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

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

brainstorm

Use before any creative work or significant changes. Activates on "brainstorm", "let's brainstorm", "deep analysis", "analyze this feature", "think through", "help me design", "explore options for", or when user asks for thorough analysis of changes, features, or architectural decisions. Guides collaborative dialogue…

umputun/cc-thingz · 87 tokens