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 agentmods add skills/mumez/smalltalk-dev-plugin/st-importnpx skills add mumez/smalltalk-dev-plugin --skill st-importgit clone --depth 1 https://github.com/mumez/smalltalk-dev-pluginWhat 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.00037 | $0.00511 |
| Opus 5 | $0.00018 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
st-import 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.
What it actually says
Import Tonel Package
Import edited Tonel files into the running Smalltalk image.
Usage
/st-import PackageName /absolute/path/to/src
Steps
With arguments: import a single package
- Call
import_packagewith the package name and absolute path to thesrc/directory - Report success or error from the result
Without arguments: import all local packages in dependency order
When no arguments are given, discover and import the full project automatically:
-
Locate the source directory — read
.projectfrom the repository root. It contains JSON-like STON syntax with asrcDirectorykey (e.g.,'srcDirectory' : 'src'). Resolve the value relative to the repository root to get the absolute path to the source directory. -
Determine import order — find the
BaselineOfpackage inside the source directory (a directory whose name starts withBaselineOf). Read theBaselineOfXXX.class.stfile inside it and parse thebaseline: specmethod. Extract:- All
package: 'PkgName'declarations → the full list of packages to import - All
requires: #('Dep1' 'Dep2' ...)clauses → the dependency edges between packages
Topologically sort the packages so that each package is imported only after all its dependencies have been imported. Import the
BaselineOfpackage first (before all others), then the sorted application packages. - All
-
Import each package — call
import_packagefor each package in the computed order, passing the absolute path to the source directory. Report the result of each import as you go.
Notes
- Always use absolute paths
- Use the package parent directory as the path — do not include the package name in the path
- Import main package before test package
- Re-import after every change
Examples
/st-import RediStick-Json /home/user/git/RediStick/src
/st-import RediStick-Json-Tests /home/user/git/RediStick/src
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 · 51 lines · 37 tokens per session scan A 35eb39401a76
st-import is a skill published in the GitHub repository mumez/smalltalk-dev-plugin (15 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 511 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.
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.
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.
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…
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…
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…
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…