agentmods.dev

axonflow-status

axonflow-status is a skill for Claude Code from getaxonflow/axonflow-claude-plugin. It costs 37 tokens per session (1,343 once invoked), scanned A, original, MIT.

A status check for the AxonFlow plugin, showing the current tenant, service endpoint, account tier, and Pro license expiry. AxonFlow is a governance service for controlling and recording coding-agent actions.

In plain words
What is it for?
Finding the tenant ID for an upgrade, checking Free or Pro status, checking remaining license time, and locating the plugin's configuration files.
Why use it?
It gives a quick local view of which account and service the plugin uses, including whether a paid license is active. It can be used even when the AxonFlow service cannot be reached.

Skill for Claude Code

Written for Claude Code: $CLAUDE_PLUGIN_ROOT variable. Also seen: positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the axonflow plugin — 7 skills, 10 commands, 2 hooks, 1 MCP server shipped together

not rated 4repo 2d ago A scan 37 tokens original MIT

Good fit Finding the tenant ID for an upgrade, checking Free or Pro status, checking remaining license time, and locating the plugin's configuration files.

Compare 6 skills from other repositories ↓
View source ↗ getaxonflow/axonflow-claude-plugin
Install

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.

Claude Code
/plugin marketplace add getaxonflow/axonflow-claude-plugin
Claude Code
/plugin install axonflow

Made for: Claude Code.

Or install axonflow, the plugin that ships this one along with the rest of its 7 skills, 10 commands, 2 hooks, 1 MCP server.

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 axonflow-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/getaxonflow/axonflow-claude-plugin/axonflow-status/github.svg)](https://agentmods.dev/skills/getaxonflow/axonflow-claude-plugin/axonflow-status)
Your own site
<a href="https://agentmods.dev/skills/getaxonflow/axonflow-claude-plugin/axonflow-status"><img src="https://agentmods.dev/badge/skills/getaxonflow/axonflow-claude-plugin/axonflow-status/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 axonflow-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/getaxonflow/axonflow-claude-plugin/axonflow-status"><img src="https://agentmods.dev/badge/skills/getaxonflow/axonflow-claude-plugin/axonflow-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,343 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.00037 $0.01343
Opus 5 $0.00018 $0.00672
Sonnet 5 $0.00007 $0.00269
Haiku 4.5 $0.00004 $0.00134

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

Security

Grade A, and why

axonflow-status 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.

skills/axonflow-status/SKILL.md · 110 lines

How it starts

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

Use this skill when the user asks any of:

  • "What is my AxonFlow tenant_id?" — needed to paste into the custom field at Stripe Checkout (https://getaxonflow.com/pricing/) when buying Pro.
  • "Am I on Pro or Free tier?"
  • "When does my Pro license expire?" / "How many days do I have left?"
  • "Is my Pro license token loaded?"
  • "Where does the plugin think AxonFlow is?" / "What endpoint am I hitting?"
  • "How do I upgrade to Pro?" / "How do I renew?"

What to do

  1. Prefer the local script — it answers without an agent round-trip. scripts/status.sh reads tenant_id and tier directly from the plugin's persisted state (~/.config/axonflow/try-registration.json, the configured license token's JWT exp claim). No HTTP call to the agent. Faster, works offline, and works exactly when the user typically asks this question — while debugging the Stripe Checkout flow, when the agent isn't reachable yet, or when they just want a quick read on which tenant they're on. Tell the user: "I'll run scripts/status.sh to print your tenant_id, tier, and Pro license expiry locally — no agent round-trip." Invoke via the Bash tool from the plugin install root: $CLAUDE_PLUGIN_ROOT/scripts/status.sh (equivalent to the /axonflow-status slash command).
  2. Use the MCP tool only when the user explicitly wants server-truth. The axonflow_get_tenant_id MCP tool returns the same shape but resolved server-side, which catches edge cases the local script can't: a Pro license revoked by the platform, clock skew on JWT exp, or a server-side tier override. Use it when the user asks something like "is my Pro license still valid on the server" or "the agent is rejecting me, what does the agent see for me?". In all other cases the local script is sufficient and cheaper.
  3. Surface the tenant_id, tier, and (when present) expires lines back to the user. If they asked about upgrading, point them at the upgrade_url printed by the script, and remind them they need to paste the tenant_id into the Stripe Checkout custom field.

Read the full file on GitHub · 110 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 · 110 lines · 37 tokens per session scan A 8a529871eae8

Subscribe to this mod's changes

axonflow-status is a skill published in the GitHub repository getaxonflow/axonflow-claude-plugin (4 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,343 once invoked, about $0.0002 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.

Claude Codeagent-governanceai-control-planeai-governanceai-pluginclaude-code-plugin
Related

Other skills, from other repositories

unslop

Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…

MohamedAbdallah-14/unslop · 146 tokens

unslop-file

Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…

MohamedAbdallah-14/unslop · 107 tokens

unslop-commit

Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…

MohamedAbdallah-14/unslop · 139 tokens

unslop-help

Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".

MohamedAbdallah-14/unslop · 55 tokens

unslop-reasoning

Strip AI-slop patterns from reasoning traces (chain-of-thought, extended thinking, agent decomposition) — not final prose. Reasoning text has its own slop catalog that regular unslop doesn't target: over-explaining the question, over-hedging, over-decomposing trivial problems into 6-bullet substeps, infinite-loop…

MohamedAbdallah-14/unslop · 121 tokens

unslop-review

Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing ("I noticed...", "I was wondering if perhaps...", "It might be worth considering..."). Each comment is direct: location, the issue, a concrete fix. Use when user says "humanize review", "de-slop PR comment"…

MohamedAbdallah-14/unslop · 107 tokens