axon: Command for Claude Code

.claude/commands/eval-axon.md

eval-axon is a command for Claude Code from rudraptpsingh/axon. It costs 0 tokens per session (1,479 once invoked), scanned A, original, MIT.

An evaluation routine for Axon, a local server that lets coding agents check the computer’s hardware while they work.

In plain words
What is it for?
Install and configure Axon, repeat real work while checking hardware status, create CPU and memory load, and inspect the resulting reports.
Why use it?
It tests whether Axon correctly reports available CPU and memory capacity, identifies resource-heavy processes, detects recovery, and summarizes session health.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is rudraptpsingh/axon's own configuration. It tells Claude Code how to work on axon itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything axon configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rudraptpsingh/axon. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rudraptpsingh/axon/master/.claude/commands/eval-axon.md
Clone the repo
git clone --depth 1 https://github.com/rudraptpsingh/axon

Made for: Claude Code.

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 eval-axon

README.md
[![agentmods](https://agentmods.dev/badge/commands/rudraptpsingh/axon/eval-axon/github.svg)](https://agentmods.dev/commands/rudraptpsingh/axon/eval-axon)
Your own site
<a href="https://agentmods.dev/commands/rudraptpsingh/axon/eval-axon"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/eval-axon/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.

agentmods 80×15 button for eval-axon

Your own site · 80×15
<a href="https://agentmods.dev/commands/rudraptpsingh/axon/eval-axon"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/eval-axon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 1,479 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.00000 $0.01479
Opus 5 $0.00000 $0.00740
Sonnet 5 $0.00000 $0.00296
Haiku 4.5 $0.00000 $0.00148

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

Security

Grade A, and why

eval-axon 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.

.claude/commands/eval-axon.md · 100 lines

How it starts

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

You are evaluating axon — a zero-cloud MCP server that gives AI coding agents real-time hardware awareness. You ARE the agent. axon is YOUR tool.

Setup

  1. Build and install axon: cargo install --path crates/axon-cli
  2. Run axon setup claude-code
  3. Verify: axon diagnose and axon query hw_snapshot

Evaluation Loop (repeat 5 times minimum)

For each iteration:

Step 1: Do real work while consulting axon

  • Before heavy tasks (cargo build, cargo test, file writes): run axon query hw_snapshot — check headroom field. If insufficient, reduce parallelism or defer.
  • During stress: run axon query process_blame — check if culprit/group/fix are accurate and actionable.
  • After stress: run axon diagnose — check if recovery is detected, if recent alerts show.
  • End of session: run axon query session_health — check if the narrative captures what happened.

Step 2: Generate stress to test detection

  • CPU stress: for i in 1 2 3 4; do yes > /dev/null & done then observe axon
  • Memory stress: python3 -c "x=[bytearray(100_000_000) for _ in range(50)]" then observe
  • Mixed: run cargo clean && cargo build --release -j 4 with yes workers simultaneously
  • Kill stress and immediately diagnose — check recovery indicator
  • I/O stress: dd if=/dev/zero of=/tmp/axon_testfile bs=1M count=4096 conv=fdatasync then observe — check if impact score reflects disk saturation
  • Gradual leak: python3 -c "import time; x=[]; [x.append(bytearray(50_000_000)) or time.sleep(2) for _ in range(20)]" — watch for slow drift detection over ~40s
  • Flap test: rapidly alternate stress and idle (5s on, 5s off, repeat 6 times) — verify no alert storm, hysteresis prevents flapping
  • Recovery test: start stress, wait 10s, kill stress, verify recovery/resolved alert fires within 10s
  • Alert verification: after stress, run axon query session_health -- check alert_count > 0; if 0, alerts are not firing when they should
  • Serve lifecycle: start axon serve via MCP stdio, run all 7 tools, verify serve process stays alive throughout, verify clean exit on stdin close
  • GPU snapshot: run axon query gpu_snapshot -- verify ok=true and detected field is present

Read the full file on GitHub · 100 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. 9d ago First seen · 100 lines · 0 tokens per session scan A ff210773f2f5

Subscribe to this mod's changes

eval-axon is a command published in the GitHub repository rudraptpsingh/axon (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,479 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-31.