axon: Command for Claude Code

.claude/commands/stress-test.md

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

A command workflow for stressing a computer's CPU, then checking whether Axon detects the resulting load and identifies the responsible processes.

In plain words
What is it for?
Use it to compare CPU and memory conditions before, during, and after running several CPU-intensive processes.
Why use it?
It provides a repeatable way to check that system monitoring reports high usage, recovery, and the process causing the load.

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/stress-test.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 stress-test

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/rudraptpsingh/axon/stress-test"><img src="https://agentmods.dev/badge/commands/rudraptpsingh/axon/stress-test.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 205 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.00205
Opus 5 $0.00000 $0.00102
Sonnet 5 $0.00000 $0.00041
Haiku 4.5 $0.00000 $0.00020

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

Security

Grade A, and why

stress-test 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 10d 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/stress-test.md · 14 lines

What it actually says

Run a quick CPU stress test and verify axon detection.

Steps:

  1. axon query hw_snapshot — record baseline CPU, RAM, headroom
  2. Start stress: for i in 1 2 3 4; do yes > /dev/null & done
  3. Wait 15 seconds for axon to collect samples
  4. axon query hw_snapshot — record stressed CPU, RAM, headroom
  5. axon query process_blame — check if yes is the culprit
  6. Kill stress: kill $(jobs -p) 2>/dev/null; pkill -f "yes" 2>/dev/null
  7. Wait 10 seconds for recovery
  8. axon query hw_snapshot — record recovery CPU, RAM, headroom

Report: baseline vs stress vs recovery comparison table. Did axon correctly identify the yes processes as the culprit? Did headroom transition appropriately? Did impact level match the actual stress?

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. 10d ago First seen · 14 lines · 0 tokens per session scan A 9a19c77430a7

Subscribe to this mod's changes

stress-test 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 205 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.