selfaware-test

A self-test command for the selfaware setup. It checks dependencies, hooks, the usage interface, Codex integration, a launchd timer, and marathon support.

In plain words
What is it for?
Use it after installing or changing selfaware to check its setup. With the Codex option, it also tests a real Codex delegation.
Why use it?
It shows whether the surrounding tools and scheduled processes are working, and identifies setup problems that need attention.

Command

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/sorbh/claude-selfaware/selfaware-test
Clone the repo
git clone --depth 1 https://github.com/Sorbh/claude-selfaware
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 188 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.00025 $0.00188
Opus 5 $0.00013 $0.00094
Sonnet 5 $0.00005 $0.00038
Haiku 4.5 $0.00003 $0.00019

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

Security

Grade A, and why

selfaware-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 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.

commands/selfaware-test.md · 15 lines

What it actually says

Run ~/.claude/skills/selfaware/scripts/selftest.sh and report the results.

If the user passed codex or --codex in the arguments ($ARGUMENTS), run it as ~/.claude/skills/selfaware/scripts/selftest.sh --codex to also exercise a real Codex delegation (~1 min).

Summarize: how many checks passed / warned / failed, then list any ✗ failures with the exact fix, and any ⚠ warnings that correspond to features the user probably wants enabled (hooks not installed, keep-alive timer off, codex probe false). If everything is green, say so plainly.

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 · 15 lines · 25 tokens per session scan A c8324c973999

Subscribe to this mod's changes

selfaware-test is a command published in the GitHub repository Sorbh/claude-selfaware (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 188 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-31.