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/netlify/axis/configure-axisnpx skills add netlify/axis --skill configure-axisgit clone --depth 1 https://github.com/netlify/axisWhat 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.00052 | $0.04724 |
| Opus 5 | $0.00026 | $0.02362 |
| Sonnet 5 | $0.00010 | $0.00945 |
| Haiku 4.5 | $0.00005 | $0.00472 |
Grade C, and why
configure-axis scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"teardown": [{ "action": "run_script", "command": "rm -rf node_modules" }], Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/netlify/axis/main/skills/configure-axis/SKILL.md \ How it starts
The opening of the file, as written. The whole thing — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure AXIS
AXIS (Agent Experience Index Score) is a synthetic testing framework for AI agents. This skill teaches you to author the two files an AXIS user maintains:
- Scenarios under
scenarios/(or any path the config points at): one JSON file per task the agent will be asked to perform. axis.config.jsonat the project root: which agents to run, where scenarios live, and what is shared across them.
When to use this skill
Trigger phrases include "set up AXIS", "add an AXIS scenario", "write an axis.config.json", "evaluate my agent with AXIS", "score my agent on X".
Before authoring, do this:
- Look for an existing
axis.config.json(oraxis.config.{js,ts}) at the project root. If one exists, read it; do not overwrite without confirmation. - List the existing scenarios directory if present. Match its naming and style.
- If no config exists, suggest running
npx @netlify/axis initfirst, or scaffold one yourself using the patterns below.
Conceptual model
For each scenario, AXIS runs every configured agent against the same prompt in an isolated workspace, then scores each run on four dimensions and produces an HTML + JSON report.
- Goal achievement (default weight 0.4): did the agent satisfy the judge's checks?
- Environment (0.2): did filesystem / shell / network operations succeed reliably?
- Service (0.2): did external services (APIs, MCP servers) respond reliably?
- Agent (0.2): were the agent's decisions sound across every tool call?
Refer to the framework's output as the AXIS Result. The acronym expands to Agent Experience Index Score.
Authoring a scenario
A scenario is a JSON file under the scenarios directory. The file path (without extension, relative to that directory) becomes the scenario's key. Only name, prompt, and judge are required.
The annotated examples below are labeled
jsoncfor documentation only. They contain// commentsand trailing commas. Real.jsonfiles do NOT support either. When copying these examples into output, strip every//comment line and every trailing comma. Plain JSON examples (in the Recipes section) are safe to copy verbatim.
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 · 382 lines · 52 tokens per session scan C 5c5d34c45a0b
configure-axis is a skill published in the GitHub repository netlify/axis (56 stars, last pushed 11d ago), licensed MIT. It adds 52 tokens to every session and 4,724 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-adapter
Scaffold a new Harbor benchmark adapter by running harbor adapter init and then guide implementation using the Adapters Agent Guide as the authoritative spec.
harbor-exec
Use when working with Harbor's harbor exec CLI workflow: compiling files, directories, or globs into Harbor tasks; running map jobs; configuring artifacts and existence-only verification; using map-reduce; writing or reviewing ExecConfig YAML/JSON/TOML; or debugging command behavior, config validation, and job outputs.
review-pr
Walk Sean through an incoming waku-agent PR or issue and present it his way — four fixed sections: what this is, why it matters, how HE can test it with you as copilot, and are we ready to merge / reply / close and why. Use whenever Sean asks to look at, test, triage, or decide on a pull request or an issue, and…
compose-graphics
Advanced Compose visuals - Material 3 Expressive motion physics, AGSL shaders (Android 13+), Canvas/DrawScope generative, graphicsLayer effects.
swiftui-motion
SwiftUI animation foundations - withAnimation, transitions, matchedGeometryEffect, PhaseAnimator, KeyframeAnimator, springs, gestures.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.