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.
/plugin marketplace add matheusPavaneli/workbenchnpx agentmods add plugins/matheuspavaneli/workbench/marketplacegit clone --depth 1 https://github.com/matheusPavaneli/workbenchGrade A, and why
workbench 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.
What it actually says
{
"name": "workbench",
"owner": {
"name": "matheusPavaneli",
"url": "https://github.com/matheusPavaneli"
},
"metadata": {
"description": "Ticket-to-PR development workflow skills. Jira, Azure DevOps and GitHub Issues, or a backlog in the repo when there is no tracker at all.",
"version": "0.7.0"
},
"plugins": [
{
"name": "workbench",
"source": "./",
"description": "Ten skills covering the path from a ticket to a pull request: triage-task, plan-change, implement-change, review-diff, write-commit, draft-pr, address-review, write-handover for the people who are not engineers, plus frame-product and trace-incident for work that starts from an idea or a symptom instead. Plans carry file:line citations that a script reopens and checks; implementation is held to the file list the plan declared. `wb next` resolves which ticket a session is on and prints the one command to run. The quality bar is detected with a stated confidence, can differ per path in a monorepo, and the audit fails a plan declared below it. Git stays read-only by default; an opt-in --execute runs only allowlisted commands, never a force-push. Works against Jira, Azure DevOps and GitHub Issues, or with no tracker at all.",
"category": "workflow",
"keywords": [
"jira",
"azure-devops",
"github-issues",
"planning",
"code-review",
"pull-request",
"quality-gates",
"monorepo"
]
}
]
}
What ships with it
1 file beside marketplace.json 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 · 30 lines scan A dc9bc9b896f7
workbench is a plugin published in the GitHub repository matheusPavaneli/workbench (1 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jira-assistant-skills
Plugin marketplace listing 1 plugin: jira-assistant-skills.
ai-sdlc-harness
AI-driven SDLC workflow harness — multi-agent dev with plan → code → review → test → PR.
allbeads
Multi-repo orchestration for AI agent workflows. Aggregate beads across repositories, manage contexts, and coordinate distributed work.
allbeads-marketplace
Multi-repo orchestration for AI agent workflows.
jira
Jira integration for issue tracking, project management, and workflow automation. Create, update, and search issues directly from Claude.
dev-day
The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean…