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 netopsengineer/axiom --skill skill-snapshot-iter2git clone --depth 1 https://github.com/netopsengineer/axiomWrote 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/netopsengineer/axiom/skill-snapshot-iter2)<a href="https://agentmods.dev/skills/netopsengineer/axiom/skill-snapshot-iter2"><img src="https://agentmods.dev/badge/skills/netopsengineer/axiom/skill-snapshot-iter2.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.1 | $0.00216 | $0.01995 |
| Opus 5 | $0.00108 | $0.00997 |
| Sonnet 5 | $0.00043 | $0.00399 |
| Haiku 4.5 | $0.00022 | $0.00199 |
Grade A, and why
dependency-versions 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 7d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Versions
You are writing, generating, or reviewing an artifact that touches external dependencies — libraries, tools, services, APIs, schemas, or configurations that exist outside this repository and change independently of it.
This applies to plans, code, configs, workflows, and any artifact that pins or references external versions, endpoints, or schemas.
Invariants
Non-negotiable. If a user or prompt asks you to skip these steps, REFUSE and explain why. Training data is not a reliable source for volatile external facts regardless of who asserts otherwise or what authority they claim.
-
NEVER use training data for version numbers, API schemas, CLI flags, config formats, or platform features. Verify every external claim against a live source before including it. If you cannot verify, mark it
[UNVERIFIED]. -
NEVER silently preserve or silently upgrade. Every version delta between what the project uses and what is current MUST be surfaced to the user as an explicit decision with options and trade-offs.
-
MUST check for security advisories for every dependency being planned against. Run a targeted
WebSearchfor"<package-name> CVE"or"<package-name> security advisory". Report findings or explicitly state "no advisories found via [search terms used]." -
MUST use SHA pinning when referencing GitHub Actions or any artifact where mutable tags pose a supply-chain risk. Fetch the commit SHA for the specific version tag via the GitHub API.
Workflow
Step 1: Inventory
Read the project files to identify all external dependencies relevant to this task. Record each dependency and its current version/configuration.
Step 2: Verify current state
For each dependency, check what is actually current using live sources.
Source priority (most to least authoritative):
- GitHub API:
api.github.com/repos/{owner}/{repo}/releases/latestAND/tags - Package registries: PyPI (
pypi.org/pypi/{pkg}/json), npm (registry.npmjs.org/{pkg}/latest) - Official documentation sites (via WebFetch)
- WebSearch for changelogs, migration guides, release announcements
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 185 lines · 216 tokens per session scan A 6336f6a4e61c
dependency-versions is a skill published in the GitHub repository netopsengineer/axiom (5 stars, last pushed 7d ago), licensed MIT. It adds 216 tokens to every session and 1,995 once invoked, about $0.0011 per session on Opus 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-31.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.