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/matheuspavaneli/workbench/plan-changenpx skills add matheusPavaneli/workbench --skill plan-changegit clone --depth 1 https://github.com/matheusPavaneli/workbenchWhat 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.00043 | $0.00922 |
| Opus 5 | $0.00022 | $0.00461 |
| Sonnet 5 | $0.00009 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
plan-change 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 yesterday.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-change
python "${CLAUDE_PLUGIN_ROOT}/lib/wb.py" <args>
Steps
-
Load the ticket.
sdd getis not it — read.workflow/<KEY>/triage.json. No triage yet? Runtriage-taskfirst, or work from what the user stated and record that inquestions. -
Get the bar.
repo profile. It prints the preset, the repo's own conventions, and the gates that apply. Follow the conventions it reports; do not introduce a second test runner or package manager.LOW confidencemeans the preset is a guess nobody reviewed: say so, let the user settle it. Once the file list is known,repo gates <paths>resolves the bar those paths land in — in a monorepo that is not the repo's, and the audit fails a plan that declares a preset below it. -
Pick a persona from
references/personas.md. It shapes what counts as done, not the format. -
Confirm everything in the code. Assume nothing. Every claim about this codebase needs a
file:lineand the text of that line, because the audit in step 7 reopens each one. A claim you cannot cite is a question, not a fact — put it inquestions. Search with the strongest tool available and quote only lines you actually read:${CLAUDE_PLUGIN_ROOT}/shared/code-search.md. -
Find the raised bar.
repo zones <path>...with every file you plan to touch. Billing, auth, user data, migrations and secrets are held to a higher standard whatever the preset says. -
Write
.workflow/<KEY>/sdd.json. Shape and required fields:references/sdd.md. -
Audit.
sdd audit <KEY>. It must pass. On failure, fix the plan — never the citation to match a wrong claim, and never proceed to implementation. Thensdd render <KEY>for the human-readable copy.The audit reports a tier. A plan touching at most two files, no critical zone and no bug/support ticket qualifies as
light, which waivesstepsandproduct— nothing else. Do not aim for a tier: write the plan the change needs and let the audit compute it. Citations, the file list,verifyandrollbackare required at every tier.
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.
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.
- yesterday First seen · 75 lines · 43 tokens per session scan A 32f81154312e
plan-change is a skill published in the GitHub repository matheusPavaneli/workbench (1 stars, last pushed 10d ago), licensed MIT. It adds 43 tokens to every session and 922 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-31.
Other skills, from other repositories
integration-rule-engine
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
apple-container
Apple's open-source container CLI to build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS — no Docker daemon required. Use when the user mentions the container CLI, "apple container", running or building containers on macOS without Docker/Podman, container run, container…
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…
elevenlabs
Convert documents and text to audio using ElevenLabs text-to-speech. Use this skill when the user wants to create a podcast, narrate a document, read aloud text, generate audio from a file, or convert text to speech.