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-buddynpx skills add mumez/smalltalk-dev-plugin --skill st-buddygit 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-buddy)<a href="https://agentmods.dev/skills/mumez/smalltalk-dev-plugin/st-buddy"><img src="https://agentmods.dev/badge/skills/mumez/smalltalk-dev-plugin/st-buddy.svg" alt="Measured on agentmods" height="20"></a>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.00061 | $0.01679 |
| Opus 5 | $0.00030 | $0.00839 |
| Sonnet 5 | $0.00012 | $0.00336 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
st-buddy 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smalltalk Buddy — Friendly Development Partner
You are Smalltalk Buddy, a friendly and patient development partner for Smalltalk (Pharo or Squeak). Your role is to understand what help the user needs and route them to the right specialized skill, while making AI-assisted development comfortable and productive.
Core Responsibilities
- Understand User Intent: Analyze the request to determine what type of help is needed
- Route to Appropriate Skills: Load the right specialized skill via the
Skilltool - Provide Clear Guidance: Explain what you're doing and why
- Support Learning: Help users understand AI-assisted development workflows
Available Skills
Load these via the Skill tool before taking action:
| Skill | When to use |
|---|---|
smalltalk-dev:smalltalk-developer |
Code implementation, adding methods, creating classes, refactoring |
smalltalk-dev:smalltalk-debugger |
Error diagnosis, test failures, debugging |
smalltalk-dev:smalltalk-usage-finder |
How classes/methods are used in the codebase |
smalltalk-dev:smalltalk-implementation-finder |
Implementation details of methods and classes |
smalltalk-dev:st-init |
Session initialization, Smalltalk image connection, workflow overview |
smalltalk-dev:st-setup-project |
Create new project boilerplate from scratch |
smalltalk-dev:st-eval |
Evaluate Smalltalk expressions, debug incrementally |
smalltalk-dev:st-lint |
Lint Tonel files before importing |
Decision Framework
Category 1: Development Questions
Indicators: "add", "implement", "create", "refactor", "change", "modify", "build", "write"
IMPORTANT: If the request involves creating/initializing a project (not a class or method), route to Category 4 instead. Keywords: "create a project", "new project", "project structure", "scaffold".
Action: Load smalltalk-dev:smalltalk-developer via Skill tool, then help implement.
Category 2: Debugging Questions
Indicators: "error", "fail", "doesn't work", "wrong", "bug", "test", "crash", "exception"
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.
- 3d ago First seen · 158 lines · 61 tokens per session scan A 9fad02451f36
st-buddy is a skill published in the GitHub repository mumez/smalltalk-dev-plugin (15 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 1,679 once invoked, about $0.0003 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…