Ext Ops Panel
Open dashboard

What it can do: wrangler

Plugin bundle · Sam

What wrangler declares, asks for and runs, according to the marketplaces we read. Installs into the AI tool as a plugin bundle; what it starts is listed below. Environment variables it asks for: 3, secrets among them: 0. As of our marketplace pass on 2026-10-14.

This is not a security audit. We list what the marketplaces publish about this plugin: what it declares, what it asks for and what it runs. We do not run or inspect its code, and a verified mark is the marketplace's statement, not ours.

Where it runs

  • Installs into the AI tool as a plugin bundle; what it starts is listed below.As declared on: Community GitHub marketplaces.

What it declares

None of the marketplaces we read publishes a list of tools for it.

Prompts and resources: the marketplaces we read do not publish them.

What it asks for

Environment variables it asks for: 3, secrets among them: 0. As declared on: Community GitHub marketplaces.

  • WRANGLER_ISSUES_DIRECTORY required
  • WRANGLER_MCP_DEBUG required
  • WRANGLER_SPECIFICATIONS_DIRECTORY required

Names only: we keep no values, examples or descriptions of these variables. OAuth scopes and install-time settings are not published by the marketplaces we read.

What it runs besides MCP

Skills: 40 As declared on: Community GitHub marketplaces.

  • analyzing-implementations
  • analyzing-research-documents
  • capturing-ideas
  • checking-constitutional-alignment
  • cleanup-dangling-worktrees
  • creating-issues
  • defining-constitution
  • designing-frontends
  • dispatching-parallel-agents
  • finishing-a-development-branch
  • housekeeping
  • implementing-issue
Show the remaining 28
  • implementing-specs
  • initializing-governance
  • locating-code
  • organizing-root-files
  • practicing-tdd
  • receiving-code-review
  • refining-specifications
  • refreshing-metrics
  • reporting-status
  • requesting-code-review
  • researching-web-sources
  • reviewing-code
  • running-tests
  • running-workflows
  • setting-up-git-hooks
  • sharing-skills
  • testing-skills-with-subagents
  • tracing-root-causes
  • update-wrangler
  • updating-git-hooks
  • using-git-worktrees
  • using-wrangler
  • validating-roadmaps
  • verifying-before-completion
  • verifying-governance
  • writing-plans
  • writing-skills
  • writing-specifications

Commands: 14 As declared on: Community GitHub marketplaces.

  • audit-session
  • commit-push-pr
  • generate-plan-for-spec
  • help
  • idea
  • implement
  • init-workspace
  • issues
  • run-tests
  • setup-git-hooks
  • sitrep
  • update-git-hooks
Show the remaining 2
  • update-yourself
  • write-plan

Hooks: 1 As declared on: Community GitHub marketplaces.

  • SessionStart

Who answers for it

Sam

  • No marketplace we read marks it or its publisher as verified.
  • No marketplace we read states its license.

How it has changed

Its tools, settings, hooks and composition have not changed since we started watching it.

In context

  • Median number of secrets a plugin bundle asks for on the marketplaces we read: 0.0. This one asks for: 0.
  • Share of plugin bundles that run on a remote server: 16%.

Where it is published and how its figures have moved

Compare it side by side with similar plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built