Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add athola/claude-night-market/plugin install abstractWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/athola/claude-night-market/validate-plugin)<a href="https://agentmods.dev/commands/athola/claude-night-market/validate-plugin"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/validate-plugin.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00326 |
| Opus 5 | $0.00011 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
validate-plugin 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 8d 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.
What it actually says
Validate Plugin Structure
This command validates a Claude Code plugin's structure against the official documentation requirements.
Usage
# Validate current directory
/validate-plugin
# Validate specific plugin
/validate-plugin ~/claude-night-market/plugins/archetypes
# Validate relative path
/validate-plugin ../my-plugin
What It Checks
The validator performs detailed checks:
Critical Requirements
.claude-plugin/plugin.jsonexists and is valid JSON- Required
namefield is present - Plugin name follows kebab-case convention
- Referenced files and paths exist
- Directories are in correct locations (not nested in
.claude-plugin/)
Warnings
- Path format (should be relative with
./) - Semantic versioning format
- Directory structure matches references
Recommendations
- Recommended metadata fields (version, description, author, license)
- Enhanced Claude configuration options
- Skill frontmatter completeness
Examples
Validate Current Plugin
cd ~/claude-night-market/plugins/archetypes
/validate-plugin
Batch Validate Multiple Plugins
for plugin in ~/claude-night-market/plugins/*; do
/validate-plugin "$plugin"
done
Implementation
Run the Python validation script:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/validate_plugin.py "${1:-.}"
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.
- 8d ago First seen · 69 lines · 22 tokens per session scan A e758411cab6f
validate-plugin is a command published in the GitHub repository athola/claude-night-market (335 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 326 once invoked, about $0.0001 per session on Opus 5. 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.
Other commands, from other repositories
bug-detective
Systematic debugging assistant with troubleshooting steps.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
debug-user-tx
Reproduce and debug a user-reported failing transaction against forked cluster state, mapping the failure back to source code.
test-and-fix
Run tests and automatically fix common issues.
debug-helper
Use when something is broken and you need it diagnosed. A build failure, a runtime crash, a blank page, an unreadable error message, or behaviour that is simply wrong. Gives one exact fix, not a list of things to try.
debug-session
Start a comprehensive debugging session.