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 agentmods add skills/pugzui/axom/axom-transformnpx skills add PugzUI/axom --skill axom-transformgit 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-transform)<a href="https://agentmods.dev/skills/pugzui/axom/axom-transform"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-transform.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00772 |
| Opus 5 | $0.00000 | $0.00386 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
axom-transform 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axom Transform Skill
Format mastery. Pipeline glue. Data flow. Connective tissue of chains. Read → Transform → Write.
⚠️ Core Mandate
Transformation is the connective tissue of chains. Read → Transform → Write. Analyze → Transform → Store. Transform turns raw data into the shape the next step expects. Use it aggressively in pipelines.
Core Capabilities
1. Format Conversion
| From | To | Parameters |
|---|---|---|
| JSON | YAML | input: {...}, output_format: "yaml" |
| YAML | JSON | input: "key: value", output_format: "json" |
| CSV | JSON | input: "a,b\n1,2", output_format: "json" |
| Any | Markdown | output_format: "markdown", optional template |
| Any | Code | output_format: "code", template: "data = ${data}" |
2. Templating (Jinja2)
{
"input": { "name": "World", "items": [1, 2, 3] },
"output_format": "markdown",
"template": "# Hello {{ name }}\n\nItems:\n{% for i in items %}- {{ i }}\n{% endfor %}"
}
3. Rule-Based Transformation
{
"input": { "old_name": "value" },
"output_format": "json",
"rules": [{ "action": "rename", "field": "old_name", "new": "new_name" }]
}
Pipeline Patterns
Config Conversion (Exec → Transform → Exec)
{
"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}"
}
}
]
}
Analysis Report → Memory (Analyze → Transform → Memory)
{
"type": "review",
"target": "src/",
"chain": [
{
"tool": "axom_mcp_transform",
"args": {
"input": "${_result}",
"output_format": "markdown",
"template": "# Review Summary\n\n{{ content }}"
}
},
{
"tool": "axom_mcp_memory",
"args": {
"action": "write",
"name": "review_report_20260222",
"content": "${_result}",
"importance": "low"
}
}
]
}
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.
- 3d ago First seen · 115 lines · 0 tokens per session scan A bfcffc918bfe
axom-transform is a skill published in the GitHub repository PugzUI/axom (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 772 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…