mx-status

mx-status is a skill for Claude Code, Codex from maxence2997/mx-harness. It costs 76 tokens per session (1,754 once invoked), scanned A, original, MIT.

A status command for the mx-flow project workflow. It reads feature specifications, decision records, plans, worktrees, and temporary files to show where each feature currently stands.

In plain words
What is it for?
Use it to list all features or inspect one feature, including its specification, plan, worktree, temporary files, progress, and next action.
Why use it?
It removes the need to search several project locations manually when work becomes hard to track. It also identifies broken workflow states and suggests concrete recovery actions.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/maxence2997/mx-harness/mx-status
Any agent
npx skills add maxence2997/mx-harness --skill mx-status
Clone the repo
git clone --depth 1 https://github.com/maxence2997/mx-harness

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mx-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-status.svg)](https://agentmods.dev/skills/maxence2997/mx-harness/mx-status)
Your own site
<a href="https://agentmods.dev/skills/maxence2997/mx-harness/mx-status"><img src="https://agentmods.dev/badge/skills/maxence2997/mx-harness/mx-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,754 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00076 $0.01754
Opus 5 $0.00038 $0.00877
Sonnet 5 $0.00015 $0.00351
Haiku 4.5 $0.00008 $0.00175

Measured 3d ago against content hash 2ea706892fb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mx-status 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 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.

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.

mx-status/SKILL.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mx-status

Trigger

/mx-status              ← show all features in current project
/mx-status <name>       ← show one specific feature

Path resolution

Resolve two base directories before any file operation:

REPO_ROOT=$(git rev-parse --show-toplevel)
PROJECT=$(basename "$REPO_ROOT")
Variable Path Contains
GLOBAL_MX ~/.mx/<project>/ <name>/spec.md, <name>/adr.md, ai-learning.md
LOCAL_MX <repo-root>/.mx/ <name>/plan.md, <name>/worktree/, <name>/tmp/

On Windows: GLOBAL_MX = %USERPROFILE%\.mx\<project>\

If the current directory is not inside a git repo, show all projects under ~/.mx/ and ask the user which one to inspect.


Step 1 — Collect features

A feature is any <name> that appears as a subdirectory in either GLOBAL_MX or LOCAL_MX.

  1. List all subdirectories under ~/.mx/<project>/ (excluding ai-learning.md)
  2. List all subdirectories under .mx/
  3. Union the two lists — a feature may appear in one or both locations

For each feature, collect:

File / path Location Meaning
spec.md ~/.mx/<project>/<name>/spec.md (GLOBAL) Brainstorm complete
adr.md ~/.mx/<project>/<name>/adr.md (GLOBAL) Architecture decision recorded
plan.md .mx/<name>/plan.md (LOCAL) Plan written
worktree/ directory .mx/<name>/worktree/ (LOCAL) Worktree created
Task lines [x] / [ ] in plan.md .mx/<name>/plan.md (LOCAL) TDD progress
tmp/review-*.md .mx/<name>/tmp/review-*.md (LOCAL) Review report exists
PR URL in plan.md .mx/<name>/plan.md (LOCAL) PR created

If <name> is given, collect only that feature.


Step 2 — Classify each feature into a stage

Apply this decision tree in order:

Stage Condition Label
0 — Nothing No spec.md not started
1 — Spec spec.md exists, no plan.md awaiting plan
2 — Plan plan.md exists, no worktree/ dir awaiting worktree
3 — TDD worktree/ exists AND at least one [ ] task in progress
4 — Review All tasks [x], no tmp/review-*.md awaiting review
5 — Triage tmp/review-*.md exists, no PR URL in plan.md awaiting triage / verify
6 — PR PR URL found in plan.md PR created

Read the full file on GitHub · 194 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 3d ago First seen · 194 lines · 76 tokens per session scan A 2ea706892fb3

Subscribe to this mod's changes

mx-status is a skill published in the GitHub repository maxence2997/mx-harness (5 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 1,754 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

manuscript-typography

Audit academic manuscripts for typographic design conventions: booktabs table style, caption placement, dashes/quotes, units and numbers, cross-reference style, page layout, typographic hierarchy, professional polish. Triggers on: "check typography", "fix formatting", "polish my paper", "check my LaTeX", "typographic…

Mathews-Tom/armory · 107 tokens

architecture-reviewer

Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports. Triggers on: "review architecture", "critique design", "audit system", "assess scalability", "enterprise readiness", "technical due diligence". NOT for diagrams, use…

Mathews-Tom/armory · 71 tokens

concept-to-video

Turn concepts into animated explainer videos using Manim (Python) with MP4/GIF output, audio overlay, multi-scene composition. Triggers on: "create a video", "animate this", "make an explainer", "manim animation", "motion graphic". NOT for React video, use remotion-video.

Mathews-Tom/armory · 70 tokens

linkedin-post-style

Writes LinkedIn posts in a direct, analytical, dry-humored technical voice with visual companion guidance. Triggers on: "write this in my style", "draft a post", "rewrite this for LinkedIn", "post about this", "how should I phrase this".

Mathews-Tom/armory · 60 tokens

manuscript-provenance

Computational provenance audit verifying every number, table, and figure in a manuscript derives from code, not manual entry. Triggers on: "check provenance", "verify reproducibility", "audit my pipeline", "are my numbers from code", "provenance audit". Companion to manuscript-review (prose audit).

Mathews-Tom/armory · 70 tokens

manuscript-review

Pre-publication manuscript audit producing a section-level refactoring report with citation hygiene and submission-readiness checks. Triggers on: "review my paper", "check before submission", "is this ready to submit", "pre-pub checklist", "refactor my paper", "check my references", "does the abstract work".

Mathews-Tom/armory · 70 tokens