<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/external_plugins, branch bump/stackhawk-api</title>
<subtitle>Official Claude Code plugin directory
</subtitle>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/'/>
<entry>
<title>Fix Context7 OAuth fallback (#6333)</title>
<updated>2026-09-30T20:11:48+00:00</updated>
<author>
<name>Tobin South</name>
<email>tobin.south@gmail.com</email>
</author>
<published>2026-09-30T20:11:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=ab024cdcfa7ca80be204acd4907656ba5a968589'/>
<id>ab024cdcfa7ca80be204acd4907656ba5a968589</id>
<content type='text'>
Remote-Dev: homespace

Co-authored-by: Fahreddin Özcan &lt;ozcanfahrettinn@gmail.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Remote-Dev: homespace

Co-authored-by: Fahreddin Özcan &lt;ozcanfahrettinn@gmail.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>imessage: surface every inbound image, not just the first</title>
<updated>2026-09-30T19:34:53+00:00</updated>
<author>
<name>dltn</name>
<email>6599399+dltn@users.noreply.github.com</email>
</author>
<published>2026-09-30T19:34:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=b6041c772138cdb3408fb4d93accd770f0ec56a1'/>
<id>b6041c772138cdb3408fb4d93accd770f0ec56a1</id>
<content type='text'>
An iMessage with several photos arrived with only the first one in the
channel tag: handleInbound took the first image attachment and stopped.
Collect every image attachment instead (same filters as before) and pass
each path in the notification meta as image_path, image_path_2,
image_path_3, ... so the model can Read all of them. A single image still
produces exactly image_path, so existing behaviour is unchanged.

Numbered keys rather than an array or a joined list: Claude Code accepts
only string values in channel meta and renders each key as an attribute
on the &lt;channel&gt; tag, so keys must be plain identifiers; one key per path
also avoids inventing a delimiter for sender-controlled filenames. The
attachments query gains ORDER BY a.ROWID so the numbering follows
attachment ROWID (creation) order. Instructions and README updated to
match; version 0.1.0 -&gt; 0.2.0 in plugin.json and package.json.

Known limits, unchanged by this patch: attachments still downloading
when the message row is first polled (filename NULL) are skipped and,
since the poll watermark has already passed the message, never picked up
later; HEIC is passed through unconverted; attachments with a NULL
mime_type still pass the image filter; no cap on images per message.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
An iMessage with several photos arrived with only the first one in the
channel tag: handleInbound took the first image attachment and stopped.
Collect every image attachment instead (same filters as before) and pass
each path in the notification meta as image_path, image_path_2,
image_path_3, ... so the model can Read all of them. A single image still
produces exactly image_path, so existing behaviour is unchanged.

Numbered keys rather than an array or a joined list: Claude Code accepts
only string values in channel meta and renders each key as an attribute
on the &lt;channel&gt; tag, so keys must be plain identifiers; one key per path
also avoids inventing a delimiter for sender-controlled filenames. The
attachments query gains ORDER BY a.ROWID so the numbering follows
attachment ROWID (creation) order. Instructions and README updated to
match; version 0.1.0 -&gt; 0.2.0 in plugin.json and package.json.

Known limits, unchanged by this patch: attachments still downloading
when the message row is first polled (filename NULL) are skipped and,
since the poll watermark has already passed the message, never picked up
later; HEIC is passed through unconverted; attachments with a NULL
mime_type still pass the image filter; no cap on images per message.
</pre>
</div>
</content>
</entry>
<entry>
<title>context7: tag the remote MCP URL with client=claude-code-plugin (+ validate path fix) (#5823)</title>
<updated>2026-09-08T18:54:59+00:00</updated>
<author>
<name>jordanecker-ant</name>
<email>jordanecker@anthropic.com</email>
</author>
<published>2026-09-08T18:54:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=bc875e80bee06bf11bd28cfc2fdf9ee563d3d2d7'/>
<id>bc875e80bee06bf11bd28cfc2fdf9ee563d3d2d7</id>
<content type='text'>
* context7: tag the remote MCP URL with client=claude-code-plugin

* validate: also trigger on vendored plugins' .mcp.json and hooks changes</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* context7: tag the remote MCP URL with client=claude-code-plugin

* validate: also trigger on vendored plugins' .mcp.json and hooks changes</pre>
</div>
</content>
</entry>
<entry>
<title>greptile: repoint to greptileai/claude-plugin (git-subdir @ greptile--v1.2.3), drop the vendored copy (#5930)</title>
<updated>2026-09-08T18:54:45+00:00</updated>
<author>
<name>jordanecker-ant</name>
<email>jordanecker@anthropic.com</email>
</author>
<published>2026-09-08T18:54:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=1967693ea9edb0334cdead64ba412e85bc990769'/>
<id>1967693ea9edb0334cdead64ba412e85bc990769</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>fix(telegram): v0.0.7 reliability rollup — state-dir, PID guard, ppid watchdog, install stdout (#1424)</title>
<updated>2026-08-13T01:03:09+00:00</updated>
<author>
<name>Noah Zweben</name>
<email>noahz@anthropic.com</email>
</author>
<published>2026-08-13T01:03:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=1e96c6b0a0f06cad576086243f3d06397c4ddf44'/>
<id>1e96c6b0a0f06cad576086243f3d06397c4ddf44</id>
<content type='text'>
* fix(telegram): honor TELEGRAM_STATE_DIR/CLAUDE_CONFIG_DIR in skills and server

The server already reads TELEGRAM_STATE_DIR for multi-bot setups, but the
/telegram:access and /telegram:configure skills hardcoded
~/.claude/channels/telegram/ in 11 places. So with a custom state dir the
skill writes access.json to the default location while the server reads
from the override — pairing and allowlist edits silently don't take effect.

Skills now resolve the state dir via shell expansion (TELEGRAM_STATE_DIR →
CLAUDE_CONFIG_DIR/channels/telegram → ~/.claude/channels/telegram) before
any read/write. Server gets the same CLAUDE_CONFIG_DIR fallback. Also adds
Bash(echo)/Bash(chmod) to configure skill's allowed-tools (chmod was already
documented but not allowlisted).

* fix(telegram): verify stale PID is a server.ts process before SIGTERM

PID files race with OS PID recycling. The lockfile from #1349 stored only a
PID; after enough churn that PID can be reassigned to anything — including
the new launch's own bun-run wrapper. SIGTERMing the wrapper closes our
stdin and triggers immediate self-shutdown ('replacing stale poller' then
'shutting down' within seconds — matches #1459 item 3).

Now check 'ps -p &lt;pid&gt; -o args=' contains 'server.ts' before killing.
execFileSync (no shell); whole block already try/catch so Windows/ps-missing
falls through to just overwriting the lockfile.

* fix(telegram): drop ppid watchdog check; redirect bun install stdout to stderr

Two v0.0.5/0.0.6 regressions causing the plugin to fail at startup:

1. The orphan watchdog's process.ppid !== bootPpid check false-fires when the
   bun-run/shell wrapper exits or execs during normal startup and we get
   reparented to init — plugin self-terminates ~5s after launch. Stdin-close
   alone is the correct signal: the kernel closes the MCP pipe on any CLI
   death regardless of intermediate wrappers, so the ppid check was both
   unnecessary and harmful. (#1467; also the actual cause of #1459 item 3
   and likely #1425.)

2. 'bun install --no-summary' in the start script writes to stdout, which is
   the MCP JSON-RPC transport. The harness sees non-JSON bytes during the
   handshake and drops the connection ('Failed to connect'). Redirect install
   output to stderr. (#1470; also explains #1425 on Windows.)

---------

Co-authored-by: Claude &lt;noreply@anthropic.com&gt;
Co-authored-by: Bryan Thompson &lt;238056179+bryan-anthropic@users.noreply.github.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* fix(telegram): honor TELEGRAM_STATE_DIR/CLAUDE_CONFIG_DIR in skills and server

The server already reads TELEGRAM_STATE_DIR for multi-bot setups, but the
/telegram:access and /telegram:configure skills hardcoded
~/.claude/channels/telegram/ in 11 places. So with a custom state dir the
skill writes access.json to the default location while the server reads
from the override — pairing and allowlist edits silently don't take effect.

Skills now resolve the state dir via shell expansion (TELEGRAM_STATE_DIR →
CLAUDE_CONFIG_DIR/channels/telegram → ~/.claude/channels/telegram) before
any read/write. Server gets the same CLAUDE_CONFIG_DIR fallback. Also adds
Bash(echo)/Bash(chmod) to configure skill's allowed-tools (chmod was already
documented but not allowlisted).

* fix(telegram): verify stale PID is a server.ts process before SIGTERM

PID files race with OS PID recycling. The lockfile from #1349 stored only a
PID; after enough churn that PID can be reassigned to anything — including
the new launch's own bun-run wrapper. SIGTERMing the wrapper closes our
stdin and triggers immediate self-shutdown ('replacing stale poller' then
'shutting down' within seconds — matches #1459 item 3).

Now check 'ps -p &lt;pid&gt; -o args=' contains 'server.ts' before killing.
execFileSync (no shell); whole block already try/catch so Windows/ps-missing
falls through to just overwriting the lockfile.

* fix(telegram): drop ppid watchdog check; redirect bun install stdout to stderr

Two v0.0.5/0.0.6 regressions causing the plugin to fail at startup:

1. The orphan watchdog's process.ppid !== bootPpid check false-fires when the
   bun-run/shell wrapper exits or execs during normal startup and we get
   reparented to init — plugin self-terminates ~5s after launch. Stdin-close
   alone is the correct signal: the kernel closes the MCP pipe on any CLI
   death regardless of intermediate wrappers, so the ppid check was both
   unnecessary and harmful. (#1467; also the actual cause of #1459 item 3
   and likely #1425.)

2. 'bun install --no-summary' in the start script writes to stdout, which is
   the MCP JSON-RPC transport. The harness sees non-JSON bytes during the
   handshake and drops the connection ('Failed to connect'). Redirect install
   output to stderr. (#1470; also explains #1425 on Windows.)

---------

Co-authored-by: Claude &lt;noreply@anthropic.com&gt;
Co-authored-by: Bryan Thompson &lt;238056179+bryan-anthropic@users.noreply.github.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>Drop the conditional reload note from discord and telegram READMEs</title>
<updated>2026-08-12T22:57:07+00:00</updated>
<author>
<name>Mohamed Hegazy</name>
<email>mhegazy@anthropic.com</email>
</author>
<published>2026-08-12T22:57:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=c5b12e00f542249d808782afbaa074b9493507b1'/>
<id>c5b12e00f542249d808782afbaa074b9493507b1</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Update install instructions to the one-command plugin install</title>
<updated>2026-08-12T22:52:07+00:00</updated>
<author>
<name>Mohamed Hegazy</name>
<email>mhegazy@anthropic.com</email>
</author>
<published>2026-08-12T22:52:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=de90047d7aff26a0e4293813ac46679404bc5286'/>
<id>de90047d7aff26a0e4293813ac46679404bc5286</id>
<content type='text'>
Claude Code's /plugin install now registers the official marketplace
automatically and activates the plugin in the same session, so the
/reload-plugins step these READMEs document is no longer needed.

discord and telegram keep a conditional note because their MCP servers
can't always be activated mid-session.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Claude Code's /plugin install now registers the official marketplace
automatically and activates the plugin in the same session, so the
/reload-plugins step these READMEs document is no longer needed.

discord and telegram keep a conditional note because their MCP servers
can't always be activated mid-session.
</pre>
</div>
</content>
</entry>
<entry>
<title>Update context7 plugin — migrate to remote MCP server (#4985)</title>
<updated>2026-08-07T21:11:11+00:00</updated>
<author>
<name>Bryan Thompson</name>
<email>238056179+bryan-anthropic@users.noreply.github.com</email>
</author>
<published>2026-08-07T21:11:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=3d0e7ededa40be93bc45a1b4efcaa4c8215a6b23'/>
<id>3d0e7ededa40be93bc45a1b4efcaa4c8215a6b23</id>
<content type='text'>
Replace the npx stdio launch of @upstash/context7-mcp with Context7's
hosted remote MCP server (https://mcp.context7.com/mcp), matching the
configuration Upstash ships in upstash/context7 (plugins/claude/context7).
Adds a README and refreshes the plugin descriptions.

Co-Authored-By: Fahreddin Özcan &lt;88107904+fahreddinozcan@users.noreply.github.com&gt;

Driver: dir-plugin-add-official</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Replace the npx stdio launch of @upstash/context7-mcp with Context7's
hosted remote MCP server (https://mcp.context7.com/mcp), matching the
configuration Upstash ships in upstash/context7 (plugins/claude/context7).
Adds a README and refreshes the plugin descriptions.

Co-Authored-By: Fahreddin Özcan &lt;88107904+fahreddinozcan@users.noreply.github.com&gt;

Driver: dir-plugin-add-official</pre>
</div>
</content>
</entry>
<entry>
<title>Migrate Asana plugin to V2 MCP server (#4895)</title>
<updated>2026-08-06T20:50:27+00:00</updated>
<author>
<name>Bryan Thompson</name>
<email>238056179+bryan-anthropic@users.noreply.github.com</email>
</author>
<published>2026-08-06T20:50:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=088bee407058d7d352e8338a2b0ad5d155f8e9f4'/>
<id>088bee407058d7d352e8338a2b0ad5d155f8e9f4</id>
<content type='text'>
* Migrate Asana plugin to V2 MCP server

The V1 beta server (https://mcp.asana.com/sse) is deprecated and shuts down
on 2026-08-05. Asana's V2 server (https://mcp.asana.com/v2/mcp) requires each
user to register their own Asana OAuth app and does not support Dynamic Client
Registration. A plugin manifest cannot carry per-user OAuth credentials, so the
bundled MCP server entry is removed in favor of a documented one-time
`claude mcp add` setup (per Asana's official Claude Code instructions).

- Remove dead V1 sse .mcp.json
- Add README with V2 OAuth setup + troubleshooting
- Add /asana-setup slash command to guide the one-time setup
- Update plugin + marketplace descriptions to reference V2

Co-Authored-By: Claude Opus 4.8 &lt;noreply@anthropic.com&gt;

* plugin-dev: stop using deprecated Asana V1 SSE endpoint in examples

The Asana V1 SSE server (https://mcp.asana.com/sse) is deprecated and shuts
down on 2026-08-05, and Asana V2 is streamable HTTP with manual OAuth — not
SSE with automatic (DCR) OAuth. Replace the Asana SSE examples in the
mcp-integration skill with neutral placeholders so the tutorial no longer
teaches a dead endpoint or implies Asana is a zero-config SSE/OAuth server.

Co-Authored-By: Claude Opus 4.8 &lt;noreply@anthropic.com&gt;

---------

Co-authored-by: Greg Dardis &lt;86272347+greg-dardis@users.noreply.github.com&gt;
Co-authored-by: Claude Opus 4.8 &lt;noreply@anthropic.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Migrate Asana plugin to V2 MCP server

The V1 beta server (https://mcp.asana.com/sse) is deprecated and shuts down
on 2026-08-05. Asana's V2 server (https://mcp.asana.com/v2/mcp) requires each
user to register their own Asana OAuth app and does not support Dynamic Client
Registration. A plugin manifest cannot carry per-user OAuth credentials, so the
bundled MCP server entry is removed in favor of a documented one-time
`claude mcp add` setup (per Asana's official Claude Code instructions).

- Remove dead V1 sse .mcp.json
- Add README with V2 OAuth setup + troubleshooting
- Add /asana-setup slash command to guide the one-time setup
- Update plugin + marketplace descriptions to reference V2

Co-Authored-By: Claude Opus 4.8 &lt;noreply@anthropic.com&gt;

* plugin-dev: stop using deprecated Asana V1 SSE endpoint in examples

The Asana V1 SSE server (https://mcp.asana.com/sse) is deprecated and shuts
down on 2026-08-05, and Asana V2 is streamable HTTP with manual OAuth — not
SSE with automatic (DCR) OAuth. Replace the Asana SSE examples in the
mcp-integration skill with neutral placeholders so the tutorial no longer
teaches a dead endpoint or implies Asana is a zero-config SSE/OAuth server.

Co-Authored-By: Claude Opus 4.8 &lt;noreply@anthropic.com&gt;

---------

Co-authored-by: Greg Dardis &lt;86272347+greg-dardis@users.noreply.github.com&gt;
Co-authored-by: Claude Opus 4.8 &lt;noreply@anthropic.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>telegram: gate /start, /help, /status behind dmPolicy (#894)</title>
<updated>2026-04-23T19:02:34+00:00</updated>
<author>
<name>Noah Zweben</name>
<email>noahz@anthropic.com</email>
</author>
<published>2026-04-23T19:02:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=5a71459c03148c5952923bcdf6d399bc4da8dc70'/>
<id>5a71459c03148c5952923bcdf6d399bc4da8dc70</id>
<content type='text'>
The bot command handlers bypassed access control — they responded to
any DM user regardless of dmPolicy, leaking bot presence and
contradicting ACCESS.md's "Drop silently. No reply." contract for
allowlist mode.

Add dmCommandGate() that applies the same disabled/allowlist checks
as gate() without the pairing side effects, and route all three
handlers through it. Also prune expired pending codes before /status
iterates them.

Fixes #854

Co-authored-by: Claude &lt;noreply@anthropic.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The bot command handlers bypassed access control — they responded to
any DM user regardless of dmPolicy, leaking bot presence and
contradicting ACCESS.md's "Drop silently. No reply." contract for
allowlist mode.

Add dmCommandGate() that applies the same disabled/allowlist checks
as gate() without the pairing side effects, and route all three
handlers through it. Also prune expired pending codes before /status
iterates them.

Fixes #854

Co-authored-by: Claude &lt;noreply@anthropic.com&gt;</pre>
</div>
</content>
</entry>
</feed>
