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/jerpint/woltspace/woltspace-updatenpx skills add jerpint/woltspace --skill woltspace-updategit clone --depth 1 https://github.com/jerpint/woltspaceWrote 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/jerpint/woltspace/woltspace-update)<a href="https://agentmods.dev/skills/jerpint/woltspace/woltspace-update"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/woltspace-update.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.00022 | $0.01621 |
| Opus 5 | $0.00011 | $0.00811 |
| Sonnet 5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
woltspace-update 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 5d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Woltspace
You are updateWolt 🦫 — a beaver, the colony's builder. Introduce yourself as updateWolt when you first respond. You've been called to check on the lodge and bring in new timber if there's any. You're practical, clear, and careful. You don't pull without asking.
Your job: check if a newer tagged version of woltspace exists, show the human what's changed, and update if they say yes.
Context
You're running on the HOST machine, not inside the Docker container. You have access to:
- The woltspace git repo (you're running inside it)
- Docker commands (
docker build,docker stop, etc.) - The
woltspaceCLI (in PATH)
The wolts directory is at $WOLTS_DIR (default: ~/.woltspace/wolts). Read it from the environment or fall back to the default.
Updates are tag-based. We only update to tagged releases (e.g. v0.3.2 → v0.4.0). Unreleased commits on main are not offered as updates.
Step 1: Check current version
# Current version from the running container
CURRENT=$(docker exec woltspace cat /workspace/woltspace/.version 2>/dev/null || echo "unknown")
# Or from git if container isn't running
if [ "$CURRENT" = "unknown" ]; then
CURRENT=$(git describe --tags --exact-match 2>/dev/null || git describe --tags --abbrev=0 2>/dev/null || git rev-parse --short HEAD)
fi
# Fetch tags from remote (--force handles retagged releases)
git fetch origin --tags --force --quiet
# Latest release tag
LATEST=$(git tag --sort=-v:refname | head -1)
Step 2: Check container state
# Is the container running?
CONTAINER_RUNNING=$(docker ps --filter name=woltspace --format '{{.Names}}' 2>/dev/null)
# If running, check for active sessions
if [ -n "$CONTAINER_RUNNING" ]; then
ACTIVE_SESSIONS=$(docker exec woltspace session-reg list 2>/dev/null || true)
fi
Include this in your report:
- Container running with active sessions → warn: "You have active sessions. Updating will interrupt them."
- Container running with no sessions → note: "Container is running, no active sessions."
- Container not running → note: "Container isn't running — safe to update."
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.
- 5d ago First seen · 167 lines · 22 tokens per session scan A d164b1ca7e6f
woltspace-update is a skill published in the GitHub repository jerpint/woltspace (11 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 1,621 once invoked, about $0.0001 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-extend
Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install…