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/rules-eval)<a href="https://agentmods.dev/commands/athola/claude-night-market/rules-eval"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/rules-eval/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/athola/claude-night-market/rules-eval"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/rules-eval.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00436 |
| Opus 5 | $0.00009 | $0.00218 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
rules-eval 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 9d 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
Rules-Eval
Evaluate and validate Claude Code rules in .claude/rules/ directories. Checks YAML frontmatter, glob patterns, content quality, and directory organization.
Invoke Skill(abstract:rules-eval), which carries the scoring, the
frontmatter and glob validations and the organization patterns.
When To Use
Use this command when you need to:
- Validate rule files before deployment
- Audit frontmatter for YAML errors or Cursor-specific fields
- Check glob patterns for syntax and specificity issues
- Assess overall rules organization and naming
When NOT To Use
Avoid this command if:
- Evaluating skills - use /skills-eval instead
- Evaluating hooks - use /hooks-eval instead
- Validating full plugin structure - use /validate-plugin instead
Usage
# Evaluate rules in current project
/rules-eval
# Evaluate specific directory
/rules-eval .claude/rules/
# Detailed analysis with per-file breakdown
/rules-eval --detailed
# Evaluate a plugin's rules
/rules-eval plugins/conserve/.claude/rules/
Implementation
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/rules_validator.py \
"${1:-.claude/rules}" \
${2:+--detailed}
Related Commands
/skills-eval- Skill quality evaluation/hooks-eval- Hook quality evaluation/validate-plugin- Complete plugin structure validation
Related Skills
- rules-eval skill (
skills/rules-eval/SKILL.md) - Detailed evaluation frameworkmodules/frontmatter-validation.md- YAML/frontmatter checksmodules/glob-pattern-analysis.md- Glob pattern validationmodules/content-quality-metrics.md- Content quality assessmentmodules/organization-patterns.md- Directory organization
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.
- 9d ago First seen · 66 lines · 18 tokens per session scan A 3d31c87e5f6d
rules-eval is a command published in the GitHub repository athola/claude-night-market (336 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 436 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
claudex
Claude writes, Codex reviews, iterate until both agree — then ship with love.
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
stats
Agreement stats — how often do Claude and Codex actually agree in this repo?
diff-review
AI-powered diff review for Solana-specific issues and code quality.
demo
A two-minute guided duet — plants bugs in a throwaway repo and lets Claude and Codex argue about them.
pr-issue-resolve
Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.