validate

validate is a command for Claude Code from athola/claude-night-market. It costs 14 tokens per session (915 once invoked), scanned A, original, MIT.

A project-audit command that checks a project's structure and configuration files against expected development practices and reports problems.

In plain words
What is it for?
Use it to inspect a project's Git setup, language-specific configuration, required files, and other initialization details, with an optional detailed report.
Why use it?
It finds missing files, incorrect settings, and setup issues before they cause trouble during development or deployment.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/my-awesome-project.

Part of the attune plugin — 14 skills, 11 commands, 2 agents shipped together

Good fit Use it to inspect a project's Git setup, language-specific configuration, required files, and other initialization details, with an optional detailed report.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add athola/claude-night-market
Claude Code
/plugin install attune

Made for: Claude Code.

Or install attune, the plugin that ships this one along with the rest of its 14 skills, 11 commands, 2 agents.

Wrote 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.

agentmods badge for validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/athola/claude-night-market/validate.svg)](https://agentmods.dev/commands/athola/claude-night-market/validate)
Your own site
<a href="https://agentmods.dev/commands/athola/claude-night-market/validate"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/validate.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 915 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00915
Opus 5 $0.00007 $0.00458
Sonnet 5 $0.00003 $0.00183
Haiku 4.5 $0.00001 $0.00092

Measured 4d ago against content hash 2b06b11af264, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

validate 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 4d 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.

plugins/attune/commands/validate.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Attune Validate Command

Check project setup against best practices, identify issues, and recommend improvements.

When To Use

Use this command when you need to:

  • Validate project structure and configurations
  • Check for missing required files or settings
  • Identify configuration issues before deployment
  • Audit project against best practices
  • Verify setup after initialization or upgrades

When NOT To Use

Avoid this command if:

  • Just initialized project (likely passing all checks)
  • Need to fix issues, not just identify them (use upgrade-project)
  • Looking for code quality issues (use linting/testing instead)
  • Validating specific component only (check component directly)

Usage

# Validate current project
/attune:validate

# Validate specific path
/attune:validate --path /path/to/project

# Show detailed report
/attune:validate --verbose

What This Command Does

  1. Detects project language and type
  2. Checks for required files and configurations
  3. Validates file contents (e.g., proper Makefile targets)
  4. Reports issues and recommendations

Validation Checks

Git Configuration

  • ✅ Git repository initialized
  • ✅ .gitignore present and complete
  • ✅ No large files tracked
  • ✅ No secrets in repository

Build Configuration

  • ✅ Makefile with standard targets (test, lint, format)
  • ✅ Dependency file present (pyproject.toml, Cargo.toml, package.json)
  • ✅ Version pinning for dependencies

Code Quality

  • ✅ Pre-commit hooks configured
  • ✅ Linter configuration present
  • ✅ Formatter configuration present
  • ✅ Type checker configured

CI/CD

  • ✅ Test workflow configured
  • ✅ Lint workflow configured
  • ✅ Type check workflow configured
  • ✅ Workflows use latest action versions

Project Structure

  • ✅ Source directory present (src/)
  • ✅ Test directory present (tests/)
  • ✅ README.md present
  • ✅ License file present

Output Format

Project Validation Report
========================
Project: my-awesome-project
Language: Python
Path: /home/user/my-awesome-project

Git Configuration
  ✅ Git repository initialized
  ✅ .gitignore present (50 patterns)

Build Configuration
  ✅ pyproject.toml present
  ✅ Makefile with 15 targets
  ⚠️  uv.lock is outdated (run: uv sync)

Code Quality
  ✅ Pre-commit hooks configured (7 hooks)
  ✅ Ruff configuration present
  ✅ MyPy strict mode enabled

CI/CD
  ✅ Test workflow (.github/workflows/test.yml)
  ✅ Lint workflow (.github/workflows/lint.yml)
  ❌ Missing: Type check workflow

Project Structure
  ✅ Source directory: src/my_awesome_project/
  ✅ Test directory: tests/
  ✅ README.md present
  ❌ Missing: LICENSE file

Score: 17/20 (85%)

Recommendations:
  1. Add .github/workflows/typecheck.yml (run: /attune:upgrade-project --component workflows)
  2. Add LICENSE file (pick one at https://choosealicense.com)
  3. Update uv.lock (run: make install)

Read the full file on GitHub · 167 lines

Changes

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.

  1. 4d ago First seen · 167 lines · 14 tokens per session scan A 2b06b11af264

Subscribe to this mod's changes

validate is a command published in the GitHub repository athola/claude-night-market (335 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 915 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-09-03.