Sigrid Axis

Sigrid Axis gives your AI coding agents Sigrid’s analysis of your own system while they work, so they can anchor each change in your measured architecture, plan what is worth fixing, catch problems before they merge, and improve the code that is already there.

An agent optimizes for the task you gave it, and it can only check part of that task by itself. It can run the tests. It cannot measure whether a unit is too complex, see a dependency on a file it never opened, or tell a real vulnerability from a false alarm without knowing how your system is deployed. Those answers need the whole system, measured the same way every time, and a model’s opinion of its own output is not that.

Sigrid Core already has those answers. Sigrid Axis puts them inside the agent’s loop.

Sigrid Core and Sigrid Axis

Sigrid Core is the analysis platform you may already know: it measures maintainability, architecture, security, reliability, and open source health, and it keeps the findings, ratings, and dependency graphs you see in the Sigrid dashboards and in Sigrid CI.

Sigrid Axis brings that analysis to AI coding agents. It consists of:

• the Sigrid Axis MCP server, which gives an agent tools that read from Sigrid Core and write triage decisions back to it;
• a set of skills, which give the agent procedures for using those tools.

MCP and skills are open standards, so Axis works in any agentic tool that supports them. Axis does not analyze anything on its own. Every rating, finding, and graph edge an agent sees through Axis comes from Sigrid Core, and every status it writes back shows up in Sigrid Core.

Axis works with Sigrid On-Premise too, through the on-premise Sigrid Axis MCP server.

The agentic lifecycle

We think of agentic development as a cycle of four phases, and Sigrid Axis does something different in each one:

• Ground: the agent learns how your system is actually wired from Sigrid Core’s dependency graph, so it acts on the real structure and spends fewer tokens getting there.
• Plan: Axis reads the current state of the system and the open findings, decides what is worth fixing, and writes that plan down.
• Prevent: Axis checks every change the agent makes against your quality, security, and architecture standards, before it reaches a commit or a merge.
• Improve: Axis fixes what the plan named, one reviewable commit at a time.

Two capabilities

Sigrid Axis has two capabilities today.

Guardrails covers the Prevent phase. It runs two checks: a quality gate on each file the agent changed, through the guardrails_quality_check MCP tool, and the architecture-drift skill on the whole change before you push it. A standing instruction tells the agent when to run each one. The change-feedback skill runs Sigrid CI on a local change for what neither check sees.

Auto-fix Agents covers the other three phases, for the problems Sigrid Core has already found:

• Ground: the explore-architecture skill and the architecture-explorer agent.
• Plan: the diagnose skill for maintainability and architecture, and the triage-findings skill for security, reliability, and open source findings.
• Improve: the autofix skill.

The setup skill sits outside both. It records which Sigrid system a repository belongs to, and every other skill reads that.

Get started

Start with installing Sigrid Axis: connect the MCP server, install the skills, and add the Guardrails instructions. The Claude Code plugin adds the one for the quality gate.

Then pick the guide for the job in front of you. Each one follows that job through on a real codebase: what to configure, what a session looks like, and how to check what the agent did.