athola/claude-night-market

COLLECTIONcommunity
atholaMITUpdated 3mo agoGitHub

23 Claude Code plugins: TDD enforcement hooks, git/PR workflows, spec-driven development, code review, project lifecycle, fix-from-error, maintenance automation, context optimization, research, and multi-LLM delegation. 186 skills, 128 commands, 54 agents.

[](book/src/plugins/) [](book/src/reference/capabilities-reference.md) 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. Requires Claude Code 2.1.16+ and Python 3.9+ for hooks. Run once after installing. Prefer one command? installs a subset. Full options…

This collection bundles
197 skills59 agents1 MCP server132 commands

⚠ The trust score below reflects the collection's repository only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
309GitHub stars
27Forks
3mo agoLast update
Package
Authorathola
LicenseMIT
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 2 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

[](book/src/plugins/) [](book/src/reference/capabilities-reference.md) 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. Requires Claude Code 2.1.16+ and Python 3.9+ for hooks. Run once after installing. Prefer one command? installs a subset. Full options are in the If the tool is unavailable, read skill files directly Night Market is built around the…

Keywords
ai-agentsarchitecture-patternsawesome-claude-codeawesome-claude-skillsclaude-agentsclaude-codeclaude-code-pluginsclaude-code-plugins-marketplaceclaude-commandsclaude-hooksclaude-skillscode-reviewgeminigit-workflowmemory-palacepythonqwenresource-optimizationspec-driven-developmenttest-driven-developmentcollection
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in memory & knowledge graphs