axom-transform

axom-transform is a skill for Claude Code, Codex from PugzUI/axom. It costs 0 tokens per session (772 once invoked), scanned A, original, MIT.

A data-conversion tool for changing information between formats such as JSON, YAML, CSV, Markdown, and code. It can also apply templates and field-renaming rules.

In plain words
What is it for?
Use it to convert configuration files, format reports, fill templates, rename fields, and pass structured data between pipeline steps.
Why use it?
It removes the need to write separate conversion code whenever one pipeline step produces data in a shape the next step cannot use.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to convert configuration files, format reports, fill templates, rename fields, and pass structured data between pipeline steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pugzui/axom/axom-transform
View source ↗ PugzUI/axom
Install

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.

Any agent
npx skills add PugzUI/axom --skill axom-transform
Clone the repo
git clone --depth 1 https://github.com/PugzUI/axom

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for axom-transform

README.md
[![agentmods](https://agentmods.dev/badge/skills/pugzui/axom/axom-transform/github.svg)](https://agentmods.dev/skills/pugzui/axom/axom-transform)
Your own site
<a href="https://agentmods.dev/skills/pugzui/axom/axom-transform"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-transform/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.

agentmods 80×15 button for axom-transform

Your own site · 80×15
<a href="https://agentmods.dev/skills/pugzui/axom/axom-transform"><img src="https://agentmods.dev/badge/skills/pugzui/axom/axom-transform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 772 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00772
Opus 5.5 $0.00000 $0.00309
Sonnet 5.5 $0.00000 $0.00154
Haiku 4.5 $0.00000 $0.00077

Measured 1mo ago against content hash bfcffc918bfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

docs/agents/skills/axom-transform/SKILL.md · 115 lines

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"
      }
    }
  ]
}

Read the full file on GitHub · 115 lines

Changes

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.

  1. 1mo ago First seen · 115 lines · 0 tokens per session scan A bfcffc918bfe

Subscribe to this mod's changes

axom-transform 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 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.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens