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.
git clone --depth 1 https://github.com/getaxonflow/axonflow-claude-pluginWrote 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-list-recent-decisions)<a href="https://agentmods.dev/commands/getaxonflow/axonflow-claude-plugin/axonflow-list-recent-decisions"><img src="https://agentmods.dev/badge/commands/getaxonflow/axonflow-claude-plugin/axonflow-list-recent-decisions/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-list-recent-decisions"><img src="https://agentmods.dev/badge/commands/getaxonflow/axonflow-claude-plugin/axonflow-list-recent-decisions.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.00030 | $0.00318 |
| Opus 5 | $0.00015 | $0.00159 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
axonflow-list-recent-decisions 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
List recent governance decisions made by AxonFlow for the current user/tenant using the list_recent_decisions MCP tool.
Optional decision filter (allow|deny|require_approval): $ARGUMENTS
If the user provided a filter, pass it as the decision argument; otherwise call without filters and let the platform return everything within the tier window.
Useful when the user asks:
- "what just got blocked?"
- "show me my recent denials"
- "what happened in the last hour?"
- "did anything need approval today?"
Tier-throttled per the platform's Free/Pro window+limit:
- SaaS Free / self-hosted Community: last 24h, max 5 rows per page
- SaaS Pro: last 30 days, max 100 rows per page
- Self-hosted Evaluation: last 14 days, max 100 rows per page
- Self-hosted Enterprise: full retention, max 1000 rows per page
Free callers exceeding the page cap will get the V1 upgrade envelope instead of decisions — render that to the user verbatim (it includes the upgrade URL and locked wording). Don't swallow it.
Present each row as a concise one-liner: <timestamp> <decision> <policy_id> on <tool_signature>.
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 · 27 lines · 30 tokens per session scan A bd20195e7625
axonflow-list-recent-decisions is a command published in the GitHub repository getaxonflow/axonflow-claude-plugin (4 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 318 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.
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.