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)<a href="https://agentmods.dev/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover"><img src="https://agentmods.dev/badge/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover/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"><img src="https://agentmods.dev/badge/commands/getaxonflow/axonflow-claude-plugin/axonflow-recover.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.00029 | $0.00341 |
| Opus 5 | $0.00015 | $0.00170 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
axonflow-recover 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.
What it actually says
Request a magic-link email so an AxonFlow Community-SaaS tenant bound to the given email can recover fresh credentials. The platform always returns 202 with a generic message regardless of whether the email exists — this is intentional anti-enumeration behavior.
Argument: $ARGUMENTS
Parse the argument as <email>. If missing or doesn't contain @, ask the user for a valid email.
Then run the plugin's recover.sh helper using the Bash tool. The helper POSTs to the agent's /api/v1/recover endpoint (no auth required — recovery is the path for users who lost their auth) and surfaces the platform's 202 message.
$CLAUDE_PLUGIN_ROOT/scripts/recover.sh '<email>'
The helper resolves the AxonFlow endpoint the same way the runtime hooks do: AXONFLOW_ENDPOINT if set, otherwise the Community SaaS at https://try.getaxonflow.com.
Surface the script's OK … line verbatim, then add:
"If a tenant is bound to that email you'll receive a magic link within a few minutes (check spam too). The link expires in 15 minutes. When you receive it, copy the
token=…value from the URL and run/axonflow-recover-verify <token>to complete recovery."
If the helper exits non-zero (network failure, IP rate-limit), surface the ERR … line verbatim.
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.
- 9d ago First seen · 25 lines · 29 tokens per session scan A d26ecba01aeb
axonflow-recover is a command published in the GitHub repository getaxonflow/axonflow-claude-plugin (4 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 341 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.