Individual skill
pro-tier-status
Report the user's current AxonFlow tier (Free or Pro), Pro license expiry date, endpoint, and whether a license token is configured. Use when the user asks "am I on Pro?", "what tier am I on?", "when does my Pro license expire?", "is my license active?", or wants to know which AxonFlow they're talking to.
plugins/getaxonflow/axonflow-codex-plugin/skills/pro-tier-status/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,537
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
The Codex plugin runs in one of two tiers:
[Credential-related source omitted]
[Credential-related source omitted]
Invoke the status surface in one of two ways:
1. **Prefer the local script — it answers without an agent round-trip.** `scripts/recover.sh status` 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/recover.sh status` to print your tenant_id, tier, and Pro license expiry locally — no agent round-trip." Invoke via `exec_command`:
```bash
bash $PLUGIN_DIR/scripts/recover.sh status
```
2. **Use the MCP tool only when the user explicitly wants server-truth.** The AxonFlow agent exposes `axonflow_get_tenant_id` via the `axonflow` MCP server (auto-discovered by Codex when `axonflow` is configured in `~/.codex/config.toml` MCP servers). It 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.