Bulletproof Skill

A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.

Written for a practitioner: someone who already uses Claude Code and wants to know what these plugins do and whether to install them. If you are new to Claude Code, start with the official docs. For the design rationale behind a plugin, see the book.

Install

Requires Claude Code 2.1.16+ and Python 3.9+ for hooks.

# Add the marketplace, then install the plugins you want
/plugin marketplace add athola/claude-night-market
/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

Run claude --init once after installing. Two other paths exist: [npx skills][skills-cli] pulls the skill files alone into .claude/skills/, without commands, agents, or hooks, and opkg i gh@athola/claude-night-market --plugins sanctum,pensive installs whole plugins from the openpackage.yml each one ships. Full options are in the Installation Guide.

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

Everyday Use

Night Market is built around the loop you already work in. A typical feature runs end to end on a handful of commands:

1. Start a feature. /attune:mission routes you through brainstorm, specify, plan, and execute phases.
2. Write the code. imbue enforces a failing test first, so the test is written before the implementation.
3. Review before you push. /full-review runs a multi-discipline pass; /refine-code cleans up duplication and dead code.
4. Ship it. /prepare-pr runs quality gates and drafts a description that says who the change is for, where it lands inside and outside the codebase, and when it is fully integrated.
5. Pick up where you left off. /catchup rebuilds context from recent git history after a break.

The commands you reach for most:

Full task-by-task walkthroughs are in the [Common Workflows Guide][workflows].

What's Inside

23 plugins in four layers. Each installs independently, and dependencies pull their shared runtime automatically.

Foundation is the base every other layer builds on: leyline (auth, quotas, error patterns, trust verification), sanctum (git, commits, PR prep, sessions), and imbue (TDD enforcement, proof-of-work, scope guarding).

Utility handles cross-cutting concerns: conserve (context and token optimization), conjure (delegation to seven external model CLIs plus a local runner), hookify (a behavioral rules engine with a security catalog), egregore (autonomous agent orchestration), herald (notifications), and oracle (local ML inference).

Domain is where the day-to-day work happens: pensive (code and architecture review), attune (project lifecycle), spec-kit (spec-driven development), parseltongue (Python), minister (GitHub issues and DORA metrics), memory-palace (knowledge organization), archetypes (architecture paradigms), gauntlet (codebase learning), phantom (computer use), scribe (documentation and slop detection), scry (recordings), tome (research), and cartograph (codebase visualization).

Meta improves the system itself: abstract (skill authoring, hook development, evaluation, and skill-stability tracking).

The full skill, command, and agent inventory is in the Capabilities Reference.

Safety

> ⚠️ Plugins run inside your Claude Code session and can read or > edit your repo, run shell commands, and call external services. > Review any plugin before installing it.

Three guards reduce the blast radius, but none replace your own review:

• TDD gates (imbue) block implementation writes that lack a failing test.