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 PugzUI/axom --skill axom-execgit clone --depth 1 https://github.com/PugzUI/axomWrote 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/pugzui/axom/axom-exec)<a href="https://agentmods.dev/skills/pugzui/axom/axom-exec"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-exec/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/pugzui/axom/axom-exec"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-exec.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.00000 | $0.00725 |
| Opus 5.5 | $0.00000 | $0.00290 |
| Sonnet 5.5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
axom-exec 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axom Exec Skill
Atomic chains. Tool abstraction. Zero wasted steps. Read → transform → write in one call. 3–7 steps ideal.
⚠️ Core Mandate
Prefer chains over sequential calls. One axom_mcp_exec
with a chain replaces three separate invocations.
Before 3+ sequential calls, use one call with chain. Saves round-trips.
Use variable substitution (${_result}) to pipe data.
Think pipelines, not scripts.
Operations
| Operation | Target | Use |
|---|---|---|
read |
File path | Load content for chaining |
write |
File path + data |
Store results |
shell |
Command string | Non-interactive CLI |
Chain Reactions: The Power Move
Each step receives the previous step's output as _result.
Pattern: Read → Transform → Write
{
"operation": "read",
"target": "config.json",
"chain": [
{
"tool": "axom_mcp_transform",
"args": { "input": "${_result}", "output_format": "yaml" }
},
{
"tool": "axom_mcp_exec",
"args": {
"operation": "write",
"target": "config.yaml",
"data": "${_result}"
}
}
]
}
Pattern: Read → Analyze → Store in Memory
{
"operation": "read",
"target": "src/main.py",
"chain": [
{
"tool": "axom_mcp_analyze",
"args": { "type": "review", "target": "${_result}", "depth": "high" }
},
{
"tool": "axom_mcp_memory",
"args": {
"action": "write",
"name": "review_main_20260222",
"content": "${_result}",
"importance": "low"
}
}
]
}
Variable Substitution
| Syntax | Meaning |
|---|---|
${_result} |
Full result from previous step |
${_result.prop} |
Nested property (JSON) |
${_result[0]} |
Array element |
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.
- 1mo ago First seen · 104 lines · 0 tokens per session scan A eec2bfb4964a
axom-exec is a skill published in the GitHub repository PugzUI/axom (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 725 tokens. 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…