Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add getaxonflow/axonflow-claude-plugin/plugin install axonflowWrote 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.
[](https://agentmods.dev/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover-verify)<a href="https://agentmods.dev/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover-verify"><img src="https://agentmods.dev/badge/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover-verify/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.
<a href="https://agentmods.dev/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover-verify"><img src="https://agentmods.dev/badge/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00022 | $0.00410 |
| Opus 5 | $0.00011 | $0.00205 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
axonflow-recover-verify 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.
What it actually says
Consume a magic-link token issued by /axonflow-recover (or the auto-sent recovery email). On success the agent mints a fresh tenant_id + secret bound to the same email and the plugin persists them locally so subsequent governed calls authenticate as the recovered tenant.
Argument: $ARGUMENTS
Parse the argument as <token>. Tokens are 64-character hex strings. If missing or shorter than 32 characters, ask the user for the token they received in the magic-link email — they should copy the token=… value from the URL, not the URL itself.
Then run the plugin's recover-verify.sh helper using the Bash tool. The helper POSTs to /api/v1/recover/verify with Content-Type: application/json (programmatic flow — no HTML page in the loop), validates the response shape, and persists the new credentials atomically to ~/.config/axonflow/try-registration.json (mode 0600 inside a 0700 directory — same file the Community-SaaS bootstrap reads on every hook invocation).
$CLAUDE_PLUGIN_ROOT/scripts/recover-verify.sh '<token>'
On success the script writes a single OK tenant_id=… email=… endpoint=… expires_at=… line followed by the platform's note and a reminder about the previous tenant's audit history. Surface those lines verbatim.
On failure (HTTP 401 = token invalid/expired/already consumed; 403 = per-email cap reached; 5xx = server error) the script exits non-zero with ERR … lines that include the platform's error message. Surface them verbatim and tell the user to start over with /axonflow-recover <email> if they still need to recover.
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.
- 10d ago First seen · 21 lines · 22 tokens per session scan A fb36b38d7466
axonflow-recover-verify is a command published in the GitHub repository getaxonflow/axonflow-claude-plugin (4 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 410 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.
Other commands, from other repositories
ai-act-incidents
Show real-world and research-demonstrated security incidents that map to a scanner dimension, EU AI Act article, or threat category. Surfaces OWASP LLM/ASI, NIST AI RMF, and MITRE ATLAS cross-references alongside published mitigations.
ai-act-scan
Scan a codebase for EU AI Act compliance evidence and gaps. Produces a dimension-scored report with per-file findings, architecture graph, and prioritized recommendations.
ai-act-article
Show which analyzers, compliance dimensions, and current findings in this codebase map to a specific EU AI Act article.
ai-act-ask
Answer an EU AI Act question grounded in the bundled knowledge base — verbatim statute text, obligation paraphrases, and the compound-risk taxonomy. Offline and deterministic by default; cites the articles it relies on.
ai-act-settings
View or change the scanner's settings — mode (deterministic vs assisted) and autoapply. Assisted mode lets the plugin use your own Claude Code for semantic scanning, grounded Q&A, and applying fixes.
ai-act-scan-fix
Scan a codebase, then propose concrete remediation (code edits, new files, tests) for the top compliance gaps. Does NOT auto-apply — always shows the plan first.