st-setup-project

A project starter for Pharo and Squeak, which are Smalltalk programming environments. It creates the basic folders and packages needed for application code and tests.

In plain words
What is it for?
Use it to start a new Smalltalk project with a BaselineOf setup, a core package, and a tests package.
Why use it?
It removes the manual work of deciding and creating the initial Smalltalk project structure. It also checks that the project name follows the required format and that an existing project is not overwritten.

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

Made for: Claude Code, Codex.

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 863 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.00080 $0.00863
Opus 5 $0.00040 $0.00432
Sonnet 5 $0.00016 $0.00173
Haiku 4.5 $0.00008 $0.00086

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

Security

Grade A, and why

st-setup-project 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-setup-project/SKILL.md · 112 lines

How it starts

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

Set Up Smalltalk Project Boilerplate

Create a complete Smalltalk project structure with BaselineOf, Core package, and Tests package.

When to Use This Skill

  • User asks to "create a new project", "start a Smalltalk project", or "set up project structure"
  • No src/ directory or .project file exists in the current directory
  • User provides a project name and wants to begin development

Project Name Rules

  • PascalCase required: Must start with uppercase, alphanumeric only
  • Valid: MyProject, RedisClient, JSONParser
  • Invalid: my-project, my_project, myProject

If no name provided: Ask with AskUserQuestion: "What is your project name? (Use PascalCase like MyProject)"

Pre-flight Checks

1. Validate PascalCase:

if [[ ! "$PROJECT_NAME" =~ ^[A-Z][a-zA-Z0-9]*$ ]]; then
  echo "Error: Project name must be in PascalCase (e.g., MyProject, RedisClient)"
  exit 1
fi

2. Check for existing project:

if [ -d "src" ] && [ "$(find src -mindepth 1 -maxdepth 1 -type d 2>/dev/null | wc -l)" -gt 0 ]; then
  echo "Error: Project already exists (src/ directory contains packages)"
  exit 1
fi

Created Structure

MyProject/
├── .project                          # srcDirectory: 'src'
└── src/
    ├── .properties                   # format: tonel
    ├── BaselineOfMyProject/
    │   ├── package.st
    │   └── BaselineOfMyProject.class.st
    ├── MyProject-Core/
    │   └── package.st
    └── MyProject-Tests/
        └── package.st

Implementation

Run the setup script with the validated project name. See Complete Setup Script for the full bash implementation.

Key files created:

.project (STON format with single quotes):

{
	'srcDirectory' : 'src'
}

src/.properties (Tonel format declaration):

{
	#format : #tonel
}

BaselineOf class defines package dependencies and groups:

  • Core group: ProjectName-Core
  • Tests group: ProjectName-Tests (requires Core)
  • all group: Core + Tests
  • default group: Core only

Read the full file on GitHub · 112 lines

Files

What ships with it

1 file 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. 2d ago First seen · 112 lines · 80 tokens per session scan A 11d2e53a2d10

Subscribe to this mod's changes

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