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 netlify/axis --skill using-axisgit clone --depth 1 https://github.com/netlify/axisWrote 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/netlify/axis/using-axis)<a href="https://agentmods.dev/skills/netlify/axis/using-axis"><img src="https://agentmods.dev/badge/skills/netlify/axis/using-axis/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/netlify/axis/using-axis"><img src="https://agentmods.dev/badge/skills/netlify/axis/using-axis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 31 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Anti-Refusal · line 122 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium MCP Rug Pull · line 20 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 221 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00065 | $0.04680 |
| Opus 5.5 | $0.00026 | $0.01872 |
| Sonnet 5.5 | $0.00013 | $0.00936 |
| Haiku 4.5 | $0.00006 | $0.00468 |
Grade A, and why
using-axis 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 15d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using AXIS
AXIS (Agent Experience Index Score) is a synthetic testing framework for AI agents. This skill is the operator's guide: how to invoke the CLI, where AXIS writes files, and how to read the scoring output.
For authoring scenarios and axis.config.json, see the configure-axis skill.
When to use this skill
Trigger phrases include "run AXIS", "run the ask suite", "what does --profile do", "compare runs", "explain this score", "which scenario regressed", "set a baseline", "where does AXIS put its reports", "what does this dimension mean".
Refer to the framework's output as the AXIS Result. The acronym is Agent Experience Index Score.
CLI commands
The binary is axis (or npx @netlify/axis without a global install).
axis init
Scaffold axis.config.json and a sample scenario, then install AXIS skills via npx skills.
| Flag | Purpose |
|---|---|
-s, --scenarios <path> |
Scenarios directory (default ./scenarios) |
-a, --agent <names> |
Comma-separated agents (e.g. claude-code,codex) |
--format <format> |
json (default), js, or ts |
-f, --force |
Overwrite existing files |
--no-skills |
Skip the automatic skills install |
axis run
Execute every scenario against every configured agent in isolated workspaces, score the results, and write a report.
| Flag | Purpose |
|---|---|
-c, --config <path> |
Config path (default discovers axis.config.{json,js,ts,mjs}) |
-s, --scenario <keys> |
Comma-separated keys with glob support (cms/*, hello-*) |
-a, --agent <names> |
Comma-separated agent names with glob support (claude-code|*) |
--scenarios / --agents |
Plural aliases for the two options above |
-p, --profile <name> |
Apply a named overlay from the config's profiles map |
--concurrency <n> |
Max parallel jobs (default 15) |
--runs <n> |
Run each pair n times; must be odd (default 1, or settings.runs) |
--failed [reportId] |
Re-run only failed pairs from a prior report (default latest) |
--no-score |
Skip the LLM judges, write raw results only |
--compare-baseline [name] |
Diff results against a saved baseline (default main) |
--refresh-skills |
Force re-clone of remote skills cached under .axis/skills-cache/ |
--refresh-repos |
Force re-clone of repos cached under .axis/repos/ for copy actions |
--json |
Emit JSON to stdout instead of the live TTY display |
-v, --verbose |
Per-step logging |
--debug |
Capture raw agent stdout into {agent}.debug.ndjson |
-o, --output-dir <dir> |
Also write the report manifest to this directory |
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.
- 15d ago Changed · +47 lines debfe4697e26
- 17d ago Changed · +7 lines · +7 tokens per session 14f78f8560f8
- 1mo ago First seen · 225 lines · 58 tokens per session scan A 993b47dce96a
using-axis is a skill published in the GitHub repository netlify/axis (64 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 4,680 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
AI System Quality Engineer
Test LLM, RAG, MCP, and agentic systems end to end. Build golden datasets, run deterministic checks and LLM judges, score retrieval, probe prompt injection, verify tool use, and gate CI on thresholds. Orchestrates DeepEval, Ragas, promptfoo, and Langfuse.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, renders app tools' views in a headless MCP Apps host, and produces a…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.