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/implement-changenpx skills add matheusPavaneli/workbench --skill implement-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.00051 | $0.00840 |
| Opus 5 | $0.00026 | $0.00420 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
implement-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
implement-change
python "${CLAUDE_PLUGIN_ROOT}/lib/wb.py" <args>
Steps
-
Read the plan's own slices, not the whole document:
sdd get <KEY> --section stepsand--section files. Nosdd.json? Runplan-changefirst. A failed audit blocks every command here by design — fix the plan, do not work around it.Picking work back up mid-way?
status <KEY>says which planned files are already changed and what is left, without re-reading the plan. -
Check where you are.
flow showreports the branch this work starts from, whether the current branch is protected, and any validation branch the commits will later be carried onto.flow start <KEY> --title "..."prints the branch name and base to use. -
Implement one step at a time, in order, touching only the listed files. Follow the repo's existing patterns. Nothing tidied, renamed or upgraded along the way: the plan's file list is the scope, and it was reviewed.
-
Write the tests the plan named.
sdd get <KEY> --section tests. Each entry says what must hold — assert that, not that a function was called. A regression test must fail without the fix; check that it does. -
Check the scope.
impl check <KEY>after each step or two. It lists planned files as changed or pending,otherfor a file another audited plan claims, andoverlapwhere two plans claim one file. It fails only on a file no audited plan accounts for. -
Verify.
impl verify <KEY>runs the plan'sverifycommands and writes.workflow/<KEY>/evidence.md. It refuses anything that is not a known test, build or lint runner — run those yourself and say so. -
Report honestly. If verification fails, say so with the failing line. Fix the code, never the evidence.
Do not re-run sdd audit to confirm your work: it checks the plan, not the
code. Re-run it when you change the plan — that now passes, reporting which
citations have drifted. impl check and impl verify are the checks for this
stage.
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 · 72 lines · 51 tokens per session scan A 6fbf4e1341b2
implement-change is a skill published in the GitHub repository matheusPavaneli/workbench (1 stars, last pushed 10d ago), licensed MIT. It adds 51 tokens to every session and 840 once invoked, about $0.0003 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…
google-calendar
Interact with Google Calendar - list calendars, view events, create/update/delete events, and find free time. Use when user asks to: check calendar, schedule a meeting, create an event, find available time, list upcoming events, delete or update a calendar event, or respond to meeting invitations. Lightweight…