What is COMMAND_COMPLIANCE_REPORT?

A report checking whether analysis command files follow the project’s required ways to call coordination tools.

Use it to review compliance, see which files were changed, and confirm that the checked commands use the expected tool format.

It makes command usage more consistent and identifies files that need updates.

COMMAND_COMPLIANCE_REPORT — Command by ruvnet

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/sublinear-time-solver/command_compliance_report

Clone the repo

git clone --depth 1 https://github.com/ruvnet/sublinear-time-solver

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 100% copy Near-identical to another mod 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.

Model	Per session	Once 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

This is a copy

100% identical to COMMAND_COMPLIANCE_REPORT — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.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

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

Recommendations

All analysis commands now follow the proper pattern
No direct bash commands or implementation calls remain
Token usage analysis properly integrated with MCP tools
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.

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/sublinear-time-solver (89 stars, last pushed 1mo ago), 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. It is 100% identical to COMMAND_COMPLIANCE_REPORT, differing in 0 lines, and is treated as a copy.

graph-laplacian iterative-solvers mcp-tools model-context-protocol numerical-linear-algebra pagerank-algorithm

COMMAND_COMPLIANCE_REPORT

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

Analysis Commands Compliance Report

Overview

Files Reviewed

1. token-efficiency.md

2. performance-bottlenecks.md

Summary

Compliance Patterns Enforced

Recommendations

What this file has done since we first saw it

Other commands, from other repositories

add-tool

OPSX: Archive

session-start

audit-web

atrs

onboard