Ext Ops Panel
Open dashboard

What it can do: dynos-audit

Plugin bundle · HassamSheikh

What dynos-audit 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. None of the marketplaces we read publishes its tools or the settings it asks for. As of our marketplace pass on 2026-10-13.

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: Claude Code: claude-plugins-community.

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

None of the marketplaces we read lists environment variables for it.

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: 21 As declared on: Claude Code: claude-plugins-community.

  • audit
  • calibration
  • dashboard
  • dry-run
  • execute
  • execution
  • global
  • init
  • investigate
  • list
  • local
  • maintain
Show the remaining 9
  • memory
  • plan
  • register
  • repair
  • residual
  • resume
  • start
  • status
  • trajectory

Agents: 37 As declared on: Claude Code: claude-plugins-community.

  • accessibility-auditor
  • api-contract-auditor
  • architecture-auditor
  • backend-executor
  • claude-md-auditor
  • code-quality-auditor
  • data-executor
  • data-integrity-auditor
  • db-executor
  • db-schema-auditor
  • dead-code-auditor
  • docs-accuracy-auditor
Show the remaining 25
  • docs-executor
  • infra-executor
  • infrastructure-auditor
  • integration-executor
  • investigator
  • investigator-legacy
  • ml-executor
  • observability-auditor
  • observability-executor
  • performance-auditor
  • planning
  • privacy-auditor
  • refactor-executor
  • release-auditor
  • release-executor
  • repair-coordinator
  • security-auditor
  • security-executor
  • spec-completion-auditor
  • supply-chain-auditor
  • test-strategy-auditor
  • testing-executor
  • threat-model-auditor
  • ui-auditor
  • ui-executor

Hooks: 5 As declared on: Claude Code: claude-plugins-community.

  • PostToolUse
  • PreToolUse
  • SessionStart
  • SubagentStop
  • TaskCompleted

Who answers for it

HassamSheikh

  • No marketplace we read marks it or its publisher as verified.
  • License: MIT.
  • The repository github.com/hassamsheikh/dynos-audit belongs to the account the publisher is listed under on Claude Code: claude-plugins-community.

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: 20%.

Where it is published and how its figures have moved

Compare it side by side with similar plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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