ddunnock-claude-plugins

A plugin marketplace entry containing 20 Claude plugins for engineering analysis, documentation, research, and specification work. The excerpt names plugins for documentation architecture, research, specification refinement, and specification generation.

In plain words
What is it for?
Finding plugins for restructuring documentation, investigating research opportunities, refining specifications, generating specification files, and related engineering tasks.
Why use it?
It groups related add-ons in one marketplace listing instead of requiring each one to be discovered separately.

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 ddunnock/claude-plugins
agentmods
npx agentmods add plugins/ddunnock/claude-plugins/marketplace
Clone the repo
git clone --depth 1 https://github.com/ddunnock/claude-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

ddunnock-claude-plugins 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.

.claude-plugin/marketplace.json · 190 lines

How it starts

The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "name": "ddunnock-claude-plugins",
  "owner": {
    "name": "dunnock"
  },
  "metadata": {
    "description": "A collection of plugins that extend Claude's capabilities with engineering analysis, documentation, and specification tools"
  },
  "plugins": [
    {
      "name": "documentation-architect",
      "source": "./skills/documentation-architect",
      "description": "Transform documentation using the Di\u00e1taxis framework",
      "version": "1.0.1"
    },
    {
      "name": "research-opportunity-investigator",
      "source": "./skills/research-opportunity-investigator",
      "description": "Research and opportunity investigation for protocols"
    },
    {
      "name": "specification-refiner",
      "source": "./skills/specification-refiner",
      "description": "Systematic analysis and refinement of specifications with SEAMS framework, sequential clarification questioning, and 9-phase workflow",
      "version": "2.0.0"
    },
    {
      "name": "speckit-generator",
      "source": "./skills/speckit-generator",
      "description": "Specification and task management with PLANS taxonomy, ADR-style decisions, SMART acceptance criteria, SEAMS clarification, anti-pattern detection (50 patterns), 4-level verification (stub detection + wiring checks), execution orchestration (deviation rules, checkpoint taxonomy, auth gates, session continuity), tech-specific designer agents, git checkpoints, and session-memory hooks. Outputs to speckit/ directory.",
      "version": "2.1.1"
    },
    {
      "name": "streaming-output",
      "source": "./skills/streaming-output",
      "description": "Handle streaming output patterns"
    },
    {
      "name": "trade-study-analysis",
      "source": "./skills/trade-study-analysis",
      "description": "Systematic trade study using DAU 9-Step Process",
      "version": "1.0.1"
    },
    {
      "name": "session-memory",
      "source": "./mcps/session-memory",
      "description": "Persistent session memory with se

Read the full file on GitHub · 190 lines

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 · 190 lines scan A c4bb31f5b755

Subscribe to this mod's changes

ddunnock-claude-plugins is a plugin published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo 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-30.