agentmods.dev

COMMAND_COMPLIANCE_REPORT

A compliance report documenting a review of command files in the `.claude/commands/analysis/` directory. It checks whether those files use the preferred agent tools and fallback commands correctly.

In plain words
What is it for?
Use it to review command-file compliance, verify MCP tool usage, inspect reported changes, and confirm that the reviewed files meet the documented standards.
Why use it?
It provides evidence that the reviewed command files follow the required tool-use patterns and identifies files that needed updates.

Command for Claude Code

92k +210 today A scan 0 tokens original MIT
View the source file ruvnet/RuView
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/ruvnet/ruview/command_compliance_report
Clone the repo
git clone --depth 1 https://github.com/ruvnet/RuView

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00420
Opus 5 $0.00000 $0.00210
Sonnet 5 $0.00000 $0.00084
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

COMMAND_COMPLIANCE_REPORT 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 2d 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.claude/commands/analysis/COMMAND_COMPLIANCE_REPORT.md · 54 lines

What it actually says

Analysis Commands Compliance Report

Overview

Reviewed all command files in .claude/commands/analysis/ directory to ensure proper usage of:

  • mcp__claude-flow__* tools (preferred)
  • npx claude-flow commands (as fallback)
  • No direct implementation calls

Files Reviewed

1. token-efficiency.md

Status: ✅ Updated Changes Made:

  • Replaced npx ruv-swarm hook session-end --export-metrics with proper MCP tool call
  • Updated to: Tool: mcp__claude-flow__token_usage with appropriate parameters
  • Maintained result format and context

Before:

npx ruv-swarm hook session-end --export-metrics

After:

Tool: mcp__claude-flow__token_usage
Parameters: {"operation": "session", "timeframe": "24h"}

2. performance-bottlenecks.md

Status: ✅ Compliant (No changes needed) Reason: Already uses proper mcp__claude-flow__task_results tool format

Summary

  • Total files reviewed: 2
  • Files updated: 1
  • Files already compliant: 1
  • Compliance rate after updates: 100%

Compliance Patterns Enforced

  1. MCP Tool Usage: All direct tool calls now use mcp__claude-flow__* format
  2. Parameter Format: JSON parameters properly structured
  3. Command Context: Preserved original functionality and expected results
  4. Documentation: Maintained clarity and examples

Recommendations

  1. All analysis commands now follow the proper pattern
  2. No direct bash commands or implementation calls remain
  3. Token usage analysis properly integrated with MCP tools
  4. Performance analysis already using correct tool format

The analysis directory is now fully compliant with the Claude Flow command standards.

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. 2d ago First seen · 54 lines · 0 tokens per session scan A 8e72f8fedc88

Subscribe to this mod's changes

COMMAND_COMPLIANCE_REPORT is a command published in the GitHub repository ruvnet/RuView (92,289 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 420 tokens. 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.

Code reviewdenseposeesp32monitoringrfwifiwifi-security
Related

Other commands, from other repositories

fix_board

Automatically diagnose and fix PlatformIO board upload/monitor issues.

FastLED/FastLED · 11 tokens

code_review_riscv

Review RISC-V assembly code for correctness and best practices.

FastLED/FastLED · 11 tokens

test

Run tests using uv run test.py with optional arguments.

FastLED/FastLED · 0 tokens

statusbar-style

Switch the status-bar style (classic / capsule / hairline).

leeguooooo/claude-code-usage-bar · 13 tokens

gh-pr

Create (or update) a Pull Request.

getsentry/sentry · 0 tokens

gh-review

Address feedback and checks in a Pull Request.

getsentry/sentry · 0 tokens