smalltalk-usage-finder

smalltalk-usage-finder is a skill for Claude Code from mumez/smalltalk-dev-plugin. It costs 139 tokens per session (1,949 once invoked), scanned A, original, MIT.

A Smalltalk code-analysis guide for Pharo and Squeak, two Smalltalk programming environments. It explains how to learn what classes and methods do by reading comments, references, examples, and source code.

In plain words
What is it for?
Use it to find a class's responsibility, locate references, discover example methods, and study how methods are used in context.
Why use it?
It helps developers understand unfamiliar Smalltalk code through its real uses instead of guessing from names alone.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the smalltalk-dev plugin — 14 skills, 2 MCP servers shipped together

Good fit Use it to find a class's responsibility, locate references, discover example methods, and study how methods are used in context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder
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.

Any agent
npx skills add mumez/smalltalk-dev-plugin --skill smalltalk-usage-finder
Clone the repo
git clone --depth 1 https://github.com/mumez/smalltalk-dev-plugin

Made for: Claude Code.

Or install smalltalk-dev, the plugin that ships this one along with the rest of its 14 skills, 2 MCP servers.

Wrote 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.

agentmods badge for smalltalk-usage-finder

README.md
[![agentmods](https://agentmods.dev/badge/skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder/github.svg)](https://agentmods.dev/skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder)
Your own site
<a href="https://agentmods.dev/skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder"><img src="https://agentmods.dev/badge/skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder/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.

agentmods 80×15 button for smalltalk-usage-finder

Your own site · 80×15
<a href="https://agentmods.dev/skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder"><img src="https://agentmods.dev/badge/skills/mumez/smalltalk-dev-plugin/smalltalk-usage-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,949 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00139 $0.01949
Opus 5.5 $0.00056 $0.00780
Sonnet 5.5 $0.00028 $0.00390
Haiku 4.5 $0.00014 $0.00195

Measured 1mo ago against content hash d4eac1a1462a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

smalltalk-usage-finder 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.

skills/smalltalk-usage-finder/SKILL.md · 290 lines

How it starts

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

Smalltalk Usage Finder

Discover how Smalltalk classes, methods, and packages are used in practice through systematic analysis of documentation, examples, and real-world code.

Core Analysis Workflows

1. Understanding Class Responsibilities

Goal: Discover what a class does and its intended purpose.

Primary Tool: get_class_comment - The authoritative source for class responsibility.

Workflow:

1. Verify class name (if uncertain): search_classes_like(query)
2. Get class comment: get_class_comment(class_name)
3. Present responsibility clearly

Example:

search_classes_like("Point")
→ ["Point", "PointArray", ...]

get_class_comment("Point")
→ "I represent an x-y pair of numbers usually designating a location on the screen."

Best practice: Always start with the class comment - it's the authoritative documentation.

2. Finding Class Usage Patterns

Goal: Learn how to use a class by examining real examples.

Primary Tools: search_references_to_class, get_method_source, list_methods

Workflow:

1. Check for example methods:
   - list_methods(package) or search_methods_like("example")
   - Filter for "exampleXXX" methods (class-side)
   - get_method_source for each example

2. Find real-world usage:
   - search_references_to_class(class_name)
   - Get source for top 5-10 references
   - Identify common patterns

3. Synthesize usage guide

Example methods convention:

  • Class-side methods in examples category
  • Named: exampleSimple, example1, exampleWithData
  • Best source for learning how to use a class

3. Finding Method Usage

Goal: Understand how a specific method is used in context.

Primary Tools: search_references, get_method_source

Challenge: Polymorphism - same method name in multiple classes.

Workflow:

1. Verify method exists: search_methods_like(method_name)
2. Find all references: search_references(method_name)
3. Filter by context:
   - Get source for each reference
   - Look for variable naming clues (e.g., "aPoint" → Point)
   - Check type comments
4. Present usage with examples

Read the full file on GitHub · 290 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 290 lines · 139 tokens per session scan A d4eac1a1462a

Subscribe to this mod's changes

smalltalk-usage-finder is a skill published in the GitHub repository mumez/smalltalk-dev-plugin (15 stars, last pushed yesterday), licensed MIT. It adds 139 tokens to every session and 1,949 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

root-cause-investigator

Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.

umputun/cc-thingz · 53 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

fix-js-globals

Fix JavaScript no-globals errors that UI5 linter reports but cannot auto-fix. Use this skill when linter outputs: no-globals rule with message "Access of global variable '...' (...)" in JS files Cases handled (linter CANNOT auto-fix): Assignments to global namespaces: sap.myNamespace = {...} Global namespace…

UI5/plugins-coding-agents · 243 tokens

scene-de-crime

Chaque erreur de code est traitée comme une scène de crime. Claude est l’investigation criminelle : sécurisation du périmètre, collecte de preuves, balistique, profilage du suspect, réquisitoire formel. Fondé sur l’absurde procédural de Kafka (Le Procès, 1925) : la machine judiciaire ne distingue pas entre un homicide…

bacoco/useless-skills · 157 tokens

dart-run-static-analysis

Execute dart analyze to identify warnings and errors, and use dart fix --apply to automatically resolve mechanical lint issues. Use during development to ensure code quality and before committing changes.

flutter/agent-plugins · 43 tokens

agents-sdk-dotnet-debugging

Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…

microsoft/Agents · 136 tokens