Agent Plugins

Practical plugins for real agent workflows

English · 简体中文

What you can do · Examples · Install · The collection · Troubleshooting

A collection of plugins that give your agent real leverage: the credentials and API knowledge to reach your systems, the command-line tools to operate them, and the procedures to do it consistently.

Every plugin is a directory in this repository. What you install is what you can read — no build step stands between the two.

What You Can Do

• Investigate production — chase an error through Alibaba Cloud SLS logs by environment and service
• Query data — run MySQL and PostgreSQL statements over saved connections, with schema discovery and parameterized values
• Process media — compress, convert, resize, upscale, and cut out images, audio, and video
• Find prompts — search, rate, and synthesize image-generation prompts from a local library
• Decide with a framework — work an ambiguous problem through an authoritative model chosen for the domain
• Keep personal execution moving — TickTick tasks and habits without opening another web UI
• Keep a codebase healthy — review standards, pre-push checks, CI flake diagnosis, docs and notes hygiene, and prose passes
• Handle credentials — read configuration redacted, and edit it through a local browser form instead of pasting secrets into chat

Example Workflows

These are the kinds of jobs this collection is built for:

• "Check recent payment failures in production logs"
• "Show me the schema for the orders table in Postgres"
• "Compress this 4K clip to 1080p and verify it plays"
• "Remove the background from these product photos"
• "Create a TickTick task for today's release checklist"
• "Fold these repeated shell steps into a reusable skill"

Requirements

• Claude Code, installed through the official docs
• Node.js 22 or newer, for the plugins that bundle a CLI. They run as node ${CLAUDE_PLUGIN_ROOT}/dist/<plugin>.mjs; prompt-forge uses the built-in node:sqlite, which is where the floor comes from

Plugins that only carry skills need nothing beyond Claude Code.

Quick Start

Install

1. Add this repository as a marketplace:

   /plugin marketplace add Sivan757/agent-plugins
   

2. Install the plugin you want:

   /plugin install database@agent-plugins
   

3. Repeat for any other plugin in the collection.

Note

Plugins install one at a time. Install only the ones you need — each one adds its descriptions to every session.

The Collection

Observe systems

Plugin	What it does
aliyunlog	Query Alibaba Cloud SLS logs, with environment and service-based lookup

Query data

Plugin	What it does
database	Run MySQL and PostgreSQL statements over saved connections — each connection carries its engine — with database and schema discovery, column listing, table profiling, and a guard on write statements

Process media

Plugin	What it does
ffmpeg	Build and verify FFmpeg and ffprobe commands for video, audio, and images
magick	Build ImageMagick workflows — conversion, resizing, mockups, compositing — and run Real-ESRGAN upscaling and withoutbg background removal as verified steps in the same pipeline

Manage prompts

Plugin	What it does
prompt-forge	Search, classify, rate, and synthesize image-generation prompts from a local library of 25k+ examples

Get advice

Plugin	What it does
consulting-advisor	Work through an ambiguous problem with an authoritative framework, chosen for the domain

Manage personal execution

Plugin	What it does
ticktick	Manage TickTick tasks, projects, tags, habits, kanban columns, and focus sessions

Work on DeepSeek Harness

Plugin	What it does
dsh-workflow	Review standards, pre-push checks, CI flake diagnosis, docs lifecycle, Agent Notes hygiene, prose and simplification passes, stacked PRs, and browser GIF demos
dsh-plugin-creator	Author, package, install, and debug DeepSeek Harness plugins in a separate repository

Manage credentials

Plugin	What it does
config-center	Inspect and edit stored plugin credentials; agent-facing reads are redacted, edits go through the browser form

How It Works

A plugin is two kinds of thing: skills that tell the agent how to do a job, and — when the job needs to talk to a service — a bundled CLI that does it. The CLI is built with esbuild, which inlines every dependency, so an installed plugin never runs npm install and carries no node_modules.

Credentials and environment state live outside this repository, in ~/.cache/agent-plugins/<plugin>/config.json. Each plugin opens a local browser form to edit them — the agent runs it as a background task, in this shape:

node "${CLAUDE_PLUGIN_ROOT}/dist/<plugin>.mjs" config --ui    # the plugin's own form
node "${CLAUDE_PLUGIN_ROOT}/dist/config-center.mjs" edit database # the shared editor

Important

Reads of stored configuration are always redacted, and no subcommand prints the cache path or a plaintext secret. The agent is expected to open the form for you rather than typing credentials.

This marketplace also curates a small number of third-party plugins alongside the local ones; see recommended external plugins.

Troubleshooting

A plugin says nothing is configured yet. The agent should open the setup form for you. If it does not, ask it to open the plugin's own form (config --ui). Configuration lives in ~/.cache/agent-plugins/<plugin>/config.json and never inside your project.

A bundled CLI fails with a module error. aliyunlog, config-center, database, prompt-forge, and ticktick run as Node programs and need Node.js 22 or newer. The skills-only plugins do not.

A plugin is missing from a running session. Check what is installed and enabled with /plugin; a plugin installed mid-session needs a restart.

You want to know what a plugin will do before installing it. Read it — each directory under plugins/ contains the SKILL.md instructions the agent receives and a plugin.config.ts with the plugin's metadata.

Development

Each directory under plugins/ is the plugin itself, and the source you edit is the artifact that ships.

plugins/   the plugins — each directory is installable as-is
docs/      development notes and decision records
scripts/   metadata generation, bundling, validation, and development helpers

bash scripts/dev.sh --list        # list plugins
bash scripts/dev.sh database      # load one plugin straight from this checkout
npm run generate:plugins          # after changing plugin.config.ts
npm run build                     # after changing CLI source
npm run validate:plugins          # every gate

Tip

bash scripts/dev.sh <plugin> loads the plugin from this working tree, so a skill or command edit takes effect after /reload-plugins — no build needed.

Adding a plugin: docs/plugin-development/authoring-a-plugin.md is the full checklist.

Resources

• Adding a plugin
• Claude Code plugin development notes
• Decision records
• Recommended external plugins
• Repository guidelines
• Discover plugins in Claude Code