Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

axiomcodegraph Skill

Repository ↗

by AxiomCodeAI★ 6931 skills

Install

What it does

Turn any codebase into a knowledge graph grounded in formal methods. Your AI agents get exact answers for any code-related task, ensure correctness, and optimize time and token usage.

  • Connects Instruction files the AI reads; connects to nothing
  • Account or key No key needed
  • Category Coding
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/axiomcodeai-axiomcodegraph.svg)](https://mcp.popnx.com/en/skills/axiomcodeai-axiomcodegraph)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 461.8KUpdated 4 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated yesterday

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.3KUpdated 4 days ago

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
axiomcodegraph
reagraphifyarchifysecurity-audit-skill
MakerAxiomCodeAImorlutoGraphify-Labstt-a1icloudflare
Skills11111
GitHub stars693461,751148,35296,75773,156
Last code changeNov 10, 2026Nov 16, 2026Nov 16, 2026Nov 15, 2026Sep 15, 2026
License–MITApache-2.0Apache-2.0MIT

1 skills (instruction sets) by AxiomCodeAI that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodexCursorGemini CLIGitHub CopilotWindsurf

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account AxiomCodeAI (organization) is only 2 months old: take extra care

  • Use and upkeep

    ★ 693 stars · code last changed Nov 10, 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    Installing the maker’s way adds hooks that run without you asking: run on the BeforeAgent event · run on the BeforeTool event · run on the AfterTool event · run on the AfterAgent event · run every time a chat starts

Checked automatically from the repo files at commit 45ee8b1 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

  1. Download from GitHub

    This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier

    Download from GitHub (whole repo) ↗

    Unzip it, then zip only the skills/axiomcode folder again. The ZIP must have a axiomcode folder with SKILL.md at the top level, no loose files

  2. Open Skills on claude.ai and upload

    +Create skillUpload a skillpick axiomcode.zip

    Open claude.ai/customize/skills ↗

  3. No Upload button? Turn on file creation first

    SettingsCapabilitiesCode execution and file creation

    Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free

Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)

Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)

Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /axiomcode or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /axiomcode or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the axiomcode folder at ~/.agents/skills/axiomcode

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick axiomcode

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick axiomcode

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

Checking the commands · copy buttons appear once they pass

Checking the commands · copy buttons appear once they pass

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: axiomcode
description: >-
  Use for any why, what or where question about code — how a codebase works, where something lives, who calls it, what a change to it breaks, which tests cover an edit. Also use when resolving an issue or bug report, which names a symptom rather than a file. Examples: "How does X work?", "Where do I change Y?", "What calls this?", "What breaks if I change Z?", "Which tests do I run?", "Fix this issue". Search with grep as usual; ask the graph for what grep cannot know — which declaration a call reaches and the callers that never spell the name. Answers come from a resolved call graph, so they include callers that never spell the name — through an interface, an override, a callback, dependency injection or a config key — and every place comes with the code of the function it sits in. Call the MCP tools directly, no need to load this skill first: impact(name) for who calls it and what a change reaches (with no name: your uncommitted edits), path(start, end) for how A reaches B, tests() for the tests your edits reach, context(task, source=True) for how something works as a step-by-step call flow with each step's code. Only when those tools are not in your list, the same from the shell: `axiomcode impact <name>`, `axiomcode path <A> <B>`, `axiomcode tests`, `axiomcode context "<task>" --source`. Java, TypeScript, Python, JavaScript, C#, and HTML + CSS (impact .class, #id, a custom property as var(…), page.html, sheet.css, page.html:LINE; each language its own graph).
---

# axiomcode

Search with grep as usual; the graph answers what grep cannot. Use the MCP tools when they are in your list (in Claude Code
`mcp__plugin_axiomcode_axiomcode__impact`, `__path`, `__tests`, `__context`); otherwise run
`<this dir>/../../plugins/axiomcode/skills/axiomcode/scripts/axiomcode <verb>` from the repository root. Same answer either way.

| the question | MCP tool | shell |
|---|---|---|
| where is the code for this task? | your own search (grep), then bring the name here | — |
| who calls X, what does changing it reach, which tests? | `impact(name)` | `axiomcode impact <name>` |
| what is the value of constant X, and who reads it? | `impact(name)` | `axiomcode impact <name>` |
| what do my uncommitted edits reach? | `impact()` | `axiomcode impact` |
| how does A reach B? | `path(start, end)` | `axiomcode path <A> <B>` |
| which tests do my edits need, and how do I run them? | `tests()` | `axiomcode tests` |
| an answer lists an unresolved call I can see the target of | `link(site, target)` | `axiomcode link <file:line> <target>` |
| how does this work, start to finish? | `context(task, source=True)` | `axiomcode context "<task>" --source` |

Names are written as in the code: `Owner.method`, `function`, `Type`, or `file.py:123` for the declaration at that
line. There is no setup step: the first question builds the graph, and it refreshes itself after every edit.

## What an answer looks like

A numbered list of places, most relevant first, each with the code of the function it sits in. `→` marks the line
that matters; a short function is shown whole.

    1. shop/pricing.py:6  [resolved · total]
       ```python
         4  def total(prices):
         5      net = sum(prices)
       → 6      return net * (1 + vat_rate())
       ```
    verified: ✓ (4 edge(s) looked up again)

Answer from the code shown; open a file only for a place whose body was cut (`…`). The tag says how sure the place
is: `resolved` is an edge the engine resolved and re-checked (`verified:`), do not re-derive it by grepping;
`one of a set` is one of several real targets; `by name` and `text` are leads, not facts; `test` marks a test;
`hop N` is how far out it is. A call the graph could not resolve is *unknown*, not absent: never report "no callers"
from an empty answer.

## impact

With a name: who calls it, what depends on it further out, and the tests that exercise it. Example:
`impact(name="PriceService.total")`. With no name: the first line is `your edits:` (each declaration you changed and
how), then the same answer for all of them. A constant answers with its value — `change: const MAX_ITEMS = 5` —
so a limit, a default or a threshold is read off the first line rather than from the file.

## path

How one declaration reaches another: every hop of the call chain, with the code at the line each call is written on.
Example: `path(start="main", end="Ledger.put")`.

## tests

The tests your uncommitted edits reach, each with its code, and a last line `run: <command>` that runs exactly those.
Example: `tests()`. It is a lower bound: a test reached only through reflection or a service loader is not listed.

## link

Answers are in three parts. CONFIRMED places are backed by an edge: `resolved` by the engine, or `asserted` by a link —
act on them. LEADS are reached only through a guess (`by name`, `by key`, `one of a set`, `text`) — check each before
relying on it. TO RESOLVE lists the calls the answer stopped at: the site as `file:line:col`, the call as written, why
the engine could not follow it (a value from `getattr`, a handler table, reflection, a callback) and the graph's
candidate targets with their `file:line`.

When the task depends on one of those sites, read the call. Only if the code makes the target CERTAIN, record it:
`link(site="app/dispatch.py:6:12", target="on_save")`, or `axiomcode link app/dispatch.py:6:12 on_save` from the shell.
A candidate is a lead: confirm it by reading the call, never link one because it is ranked first. From then on impact,
path and tests walk that edge, labelled `[asserted]`, never `resolved`; when the target declares a return type, the
calls made on its result (chained, or on a variable assigned from it) resolve too. When a lead at a site is wrong,
reject it: `link(site, "not:<target>")` — it is no longer walked; only a guess can be rejected, never an edge the
engine resolved. The links are kept in `axiomcode-links.tsv` at the repository root, which is worth committing.
`link()` with no arguments lists them and whether the graph took each one; `axiomcode link <file:line:col> -` removes
one. A link is refused when the call written there names a different declaration, or the target is not one; when
the line it was made on is edited, it is dropped and listed as stale, and the site is to resolve again. Never link a
guess: an asserted edge is trusted by every answer after it.

## context

How something works, from a task in your own words: the files and callables the task touches and, for a
how-does-X-work question, the call flow step by step. Example: `context(task="how is an invoice settled",
source=True)` — source carries each step's code, so the flow is read without opening files. Only English task
words land (the graph's vocabulary is the code's identifiers); any language works once the task includes one
identifier as written in the code.

## index

`axiomcode index` builds the graph explicitly; `--lang` and `--src` narrow it. Never re-run it on an
existing graph: the graph rebuilds itself after edits, and an answer given before that finishes says so on a
`graph refresh:` line.

By default the graph is built without the project's dependencies: a call into one is unresolved or named only as an
external boundary. When better coverage is needed, compile the dependencies and enable them with `--library`, given
once on `index` and kept by every rebuild after it:

    axiomcode index --library auto                                  # the dependencies the project imports
    axiomcode index --library .venv/lib/python3.12/site-packages/requests,/deps/ir/jdk   # or name them

`auto` finds what the project depends on, in every language: a Python package its source imports, in its virtual
environment (`.venv`, `venv`, `$VIRTUAL_ENV`); a JavaScript / TypeScript package it imports, under `node_modules`; in a
Deno project, every `jsr:`, `npm:` and URL module it imports, from Deno's cache (`deno install` fetches them); a
Java dependen

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
693
Maker
AxiomCodeAI
License
Not stated
Last code change
Nov 10, 2026
SKILL.md files in the repo (including translated copies and templates)
2
Topics
ai-agents, ai-skills, antigravity, ast, change-impact-analysis, claude-code, code-analysis, code-search, codegraph, codex, cursor, formal-methods