Claude Night Market

A plugin marketplace for Claude Code, Anthropic's
agentic coding tool.

Night Market extends Claude Code with 23 plugins
covering git workflows, code review, spec-driven
development, architecture selection, codebase
visualization, autonomous agents, multi-LLM delegation,
ML-enhanced scoring, and multi-source research.
182 skills, 126 slash commands, and 54 agents.
Each plugin installs independently.

Contents

• Quick Start
• Architecture (plugin catalog, layer model)
• Common Workflows
• Requirements
• What's New
• Plugin Development
• Documentation
• Stewardship · Contributing · License

Quick Start

Requires Claude Code 2.1.16+ and Python 3.9+ for hooks.
See Requirements for details.

# Add the marketplace
/plugin marketplace add athola/claude-night-market

# Install plugins you need
/plugin install sanctum@claude-night-market    # Git workflows
/plugin install pensive@claude-night-market    # Code review
/plugin install spec-kit@claude-night-market   # Spec-driven dev

# Use them
/prepare-pr                                    # Prepare a pull request
/full-review                                   # Run code review

Alternative: Install via npx with
npx skills add athola/claude-night-market (installs all plugins at once).

After installation, run claude --init for one-time setup.

Note: If the Skill tool is unavailable, read skill files directly
at plugins/{plugin}/skills/{skill-name}/SKILL.md.

Trust & safety: plugins run inside your Claude Code session and can
read or edit your repo. Night Market ships with TDD gates (imbue),
destructive-command blockers (conserve), and additive-bias audits on
every change, but you should still review any plugin before installing it.
See STEWARDSHIP.md for the maintenance contract.

opkg (OpenPackage)

# Install specific plugins
opkg i gh@athola/claude-night-market --plugins sanctum
opkg i gh@athola/claude-night-market --plugins pensive,conserve

# Plugins that depend on shared runtime skills (e.g. attune, conjure)
# automatically pull packages/core as a dependency

See the Installation Guide
for detailed setup options.

Architecture

23 internal plugins in four layers, plus external
plugins from the superpowers-marketplace.
Arrows show dependency direction (A --> B means
A depends on B). Dashed arrows mark optional
complements.

_{Source: assets/architecture.d2 — regenerate with d2 assets/architecture.d2 assets/architecture-light.svg}

Plugin Catalog

Full inventory:
Capabilities Reference.

How the Layers Work

Governance. imbue enforces TDD via a PreToolUse hook that
verifies test files before allowing implementation writes.
Quality gates halt execution when tests fail.

Security. leyline manages OAuth flows with local token
caching. conserve auto-approves safe commands while blocking
destructive operations. sanctum isolates named sessions, and
agents can run in worktree isolation for parallel execution.

Orchestration. egregore manages autonomous agent lifecycles
with parallel worktree execution, agent specialization, cross-item
learning, and crash recovery via watchdog monitoring.

Maintenance. /update-ci reconciles pre-commit hooks and
GitHub Actions with code changes. abstract tracks skill
stability and auto-triggers improvement agents when degradation
is detected.

Cross-session state. attune, spec-kit, and sanctum
persist state across sessions via CLAUDE_CODE_TASK_LIST_ID.
GitHub Discussions serve as a second persistence layer for
decisions, war-room deliberations, and evergreen knowledge.

Risk classification. leyline:risk-classification provides
4-tier task gating (GREEN/YELLOW/RED/CRITICAL). RED and CRITICAL
tasks escalate to war-room-checkpoint for expert deliberation.

Common Workflows

See the Common Workflows Guide for full details.

Requirements

• Claude Code 2.1.16+ (2.1.32+ for agent teams, 2.1.38+ for
  security features, 2.1.85+ latest tested)
• Python 3.9+ for hooks (macOS ships 3.9.6). Plugin packages may
  target 3.10+ via virtual environments, but all hook code must be
  3.9-compatible. See the Plugin Development Guide
  for compatibility rules.

What's New

1.9.2: the imbue vow hooks split read-budget
accounting from write-reset accounting so write-heavy sessions no longer
pay a Python startup tax on every Write/Edit. Set VOW_SHADOW_MODE=0
to turn the bounded-reads vow from warn-only into a hard block. The
abstract plugin now posts PR review findings to GitHub Discussions as
Insights and filters synthetic sessions out of its Phase 6a learning
summaries.

See the Changelog for the full history.

Plugin Development

Create a new plugin:

make create-plugin NAME=my-plugin
make validate
make lint && make test

Plugin layout:

my-plugin/
├── .claude-plugin/
│   └── plugin.json        # Metadata: skills, commands, agents, hooks
├── commands/               # Slash commands (markdown)
├── skills/                 # Agent skills (SKILL.md + modules/)
├── hooks/                  # Event handlers (Python, 3.9-compatible)
├── agents/                 # Specialized agent definitions
├── tests/                  # pytest suite
├── Makefile                # Build, test, lint targets
└── pyproject.toml          # Package config

See the Plugin Development Guide for structure requirements
and naming conventions. For LSP integration, see the
LSP Guide.

Documentation

• Installation Guide -
  setup, marketplace, post-install hooks
• Quick Start -
  first commands after installation
• Common Workflows - task-oriented usage guide
• Plugin Development Guide - creating and testing plugins
• Capabilities Reference -
  full skill, command, and agent inventory
• Tutorials -
  PR workflows, debugging, feature lifecycles
• Architecture Decision Records -
  design rationale and trade-off documentation

Per-plugin documentation lives in book/src/plugins/
(one page per plugin).

Stewardship

Every plugin is entrusted to the community. Five principles guide how
we maintain and improve the ecosystem: steward (not own), multiply (not
merely preserve), be faithful in small things, serve those who come
after, and think seven iterations ahead.

Each plugin README includes a Stewardship section with specific
improvement opportunities. Run /stewardship-health to view per-plugin
health dimensions.

See STEWARDSHIP.md for the full manifesto.

Contributing

Each plugin maintains its own tests and documentation. Run make test
at the repo root to execute all plugin test suites. See the
Plugin Development Guide for contribution guidelines.

Star History

Powered by Night Market

Using night-market plugins in your project? Add the badge:

[![Powered by Night Market](https://img.shields.io/badge/powered_by-Night_Market-blueviolet)](https://github.com/athola/claude-night-market)

License

MIT