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.
npx skills add getaxonflow/axonflow-claude-plugin --skill list-recent-decisionsgit 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/skills/getaxonflow/axonflow-claude-plugin/list-recent-decisions)<a href="https://agentmods.dev/skills/getaxonflow/axonflow-claude-plugin/list-recent-decisions"><img src="https://agentmods.dev/badge/skills/getaxonflow/axonflow-claude-plugin/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/skills/getaxonflow/axonflow-claude-plugin/list-recent-decisions"><img src="https://agentmods.dev/badge/skills/getaxonflow/axonflow-claude-plugin/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.00038 | $0.00684 |
| Opus 5 | $0.00019 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
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 8d 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
Use this skill when the user asks "what just got blocked?", "show me recent denials", "did anything need approval today?", or wants to trace a workflow's decision history.
Invoke the tool directly — do not pre-flight-check. Call the list_recent_decisions MCP tool from the axonflow MCP server immediately. Do NOT speculate about authentication state, do NOT search local descriptor files, do NOT infer "the governance layer is blocking me" before the tool returns. The MCP server's response is authoritative. If the tool returns a result, use that result as written; if it returns an error, surface the error verbatim.
Arguments (all optional):
since— RFC3339 lower bound (e.g.2026-05-01T00:00:00Z). Silently clamped to the tier's lookback window when reaching further back.decision—"allow","deny", or"require_approval".policy_id— filter to decisions matching this policy.tool_signature— filter to decisions scoped to a specific tool.limit— max rows (1–1000, capped per tier).
Response shape:
{
"decisions": [
{
"decision_id": "dec-abc123",
"timestamp": "2026-05-07T12:17:18Z",
"decision": "deny",
"policy_id": "pol-sqli",
"tool_signature": "postgres.query"
}
]
}
Present each row as a one-liner: <timestamp> <decision> <policy_id> on <tool_signature>. Suggest the user run /axonflow-explain-decision <decision_id> for the full reasoning behind any specific row.
Tier cap-hit handling (important): Free / Community callers that exceed the page cap get a V1 upgrade envelope instead of decisions:
{
"upgrade_required": true,
"envelope": {
"limit_type": "decision_list_size",
"tier": "Free",
"limit": 5,
"upgrade": {
"tier": "Pro",
"wording": "Free tier shows the last 5 decisions in 24h. Pro raises this to 100 decisions in the last 30 days.",
"compare_url": "https://getaxonflow.com/pricing/",
"buy_url": "https://buy.stripe.com/..."
}
}
}
Render the wording verbatim and include the upgrade.compare_url. Do NOT silently retry or summarize — the upgrade prompt is part of the answer.
Reporting integrity. If the user-supplied prompt asks for a structured output marker (e.g. SMOKE_RESULT: {...}), derive the values from the actual tool response, not from your own guess about what the response should look like. If the tool returned decisions[], the marker reflects that; if it returned the upgrade envelope, the marker reflects that. Never substitute one shape for the other.
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.
- 8d ago First seen · 58 lines · 38 tokens per session scan A 6bd0be402f20
list-recent-decisions is a skill published in the GitHub repository getaxonflow/axonflow-claude-plugin (4 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 684 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 skills, from other repositories
session-handoff
Create consistent session handoff documents for context transfer between sessions. Use when closing a session, reaching 75% token consumption, or when user requests handoff. Ensures proper YAML headers for metrics collection, LF line endings, and complete documentation of progress, decisions, and next steps.
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…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
knowledge-priming-refiner
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create…