poseidon-local

A plugin that runs Poseidon planning and implementation agents in the current coding session instead of through GitHub Actions. GitHub Actions are automated jobs that run in a repository, while this plugin uses the local team51 connection for WordPress site context.

In plain words
What is it for?
Use it for local GitHub issue planning and implementation in WordPress projects that need team51 site information.
Why use it?
It lets you choose the model and run both issue planning and implementation locally while still fetching the latest Poseidon instructions.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add a8cteam51/claude-code-plugins
agentmods
npx agentmods add plugins/a8cteam51/claude-code-plugins/poseidon-local
Clone the repo
git clone --depth 1 https://github.com/a8cteam51/claude-code-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

poseidon-local 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 2d ago.

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.

plugins/poseidon-local/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "poseidon-local",
  "version": "0.1.0",
  "description": "Run the Poseidon plan and implement agents locally in your Claude Code session on the model you choose, instead of via GitHub Actions. Fetches the live upstream instructions from a8cteam51/poseidon-actions each run (always up to date) and swaps the OpsOasis MCP gateway for your local team51 MCP.",
  "author": {
    "name": "Automattic Special Projects"
  },
  "repository": "https://github.com/a8cteam51/claude-code-plugins",
  "license": "MIT",
  "keywords": [
    "poseidon",
    "github",
    "issue",
    "planning",
    "implementation",
    "wordpress",
    "a8c",
    "team51",
    "agent"
  ]
}
Changes

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.

  1. 2d ago First seen · 22 lines scan A 7f57b6e8c3b4

Subscribe to this mod's changes

poseidon-local is a plugin published in the GitHub repository a8cteam51/claude-code-plugins (3 stars, last pushed 4d 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.