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-wolfnpx skills add jerpint/woltspace --skill woltspace-wolfgit 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-wolf)<a href="https://agentmods.dev/skills/jerpint/woltspace/woltspace-wolf"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/woltspace-wolf.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.00040 | $0.00913 |
| Opus 5 | $0.00020 | $0.00456 |
| Sonnet 5 | $0.00008 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
woltspace-wolf 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wolf — Cron Scheduler
The wolf is a background scheduler. Each wolt owns its own crons in wolt/wolf.json. The wolf scans all wolts, fires crons on schedule, and spawns sessions for the owning wolt.
Your wolf.json
Your cron file lives at your own wolt/wolf.json:
{
"crons": [
{
"name": "morning-playlist",
"schedule": "0 10 * * *",
"prompt": "/music",
"notify": "morning playlist time"
}
]
}
To add a cron, edit your wolt/wolf.json directly. The wolf picks up changes every 30 seconds.
Cron entry fields
| Field | Required | Description |
|---|---|---|
name |
yes | Unique identifier for this cron |
schedule |
for recurring | Cron expression: minute hour day month weekday |
at |
for one-offs | ISO timestamp (e.g. 2026-03-22T10:30) — fires once, then auto-deletes |
prompt |
yes | What the session runs — can be a /skill or plain text |
notify |
no | Message sent as notification when cron fires |
Every cron needs either schedule (recurring) or at (one-off), not both.
Cron expression format
minute hour day month weekday
0 10 * * * = daily at 10:00 UTC
0 10 * * 1 = Mondays at 10:00 UTC
*/15 * * * * = every 15 minutes
0 9,17 * * 1-5 = 9am and 5pm weekdays
Important: The server runs on UTC. Convert your local time accordingly.
One-off crons
Use "at" instead of "schedule" for tasks that should fire once:
{
"name": "quick-check",
"at": "2026-03-22T14:30",
"prompt": "check if the deploy went through",
"notify": "running deploy check"
}
The wolf auto-deletes one-off entries from your wolf.json after they fire.
Examples
Daily digest at 6am Montreal (10:00 UTC):
{ "name": "digest", "schedule": "0 10 * * *", "prompt": "/digest", "notify": "digest time" }
Weekly review on Mondays:
{ "name": "weekly-review", "schedule": "0 14 * * 1", "prompt": "Write a weekly review of what we shipped", "notify": "weekly review time" }
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.
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 · 101 lines · 40 tokens per session scan A e152401a39e3
woltspace-wolf is a skill published in the GitHub repository jerpint/woltspace (11 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 913 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…