LoopX is a provider-neutral control plane that gives long-running AI-agent work persistent state, decisions, governance, recovery, and handoffs across different agent harnesses. It is for managing and reviewing durable work performed by Codex, Claude Code, Cursor, dsh, or custom agent systems.
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 huangruiteng/loopx --skill loopx-change-qualitygit clone --depth 1 https://github.com/huangruiteng/loopxWrote 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/huangruiteng/loopx/loopx-change-quality)<a href="https://agentmods.dev/skills/huangruiteng/loopx/loopx-change-quality"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-change-quality/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/huangruiteng/loopx/loopx-change-quality"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-change-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.01841 |
| Opus 5.5 | $0.00030 | $0.00736 |
| Sonnet 5.5 | $0.00015 | $0.00368 |
| Haiku 4.5 | $0.00007 | $0.00184 |
Grade A, and why
loopx-change-quality 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 1mo 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LoopX Change Quality
Use this skill only when the selected goal's
change_quality_qualification.enabled policy is true. LoopX owns the canonical
source but does not install it globally. Install a managed copy in a connected
project for the relevant host:
loopx project-skill install \
--project . \
--skill loopx-change-quality \
--surface codex \
--execute
Use --surface claude-code or --surface opencode for those hosts. Skill
discovery does not activate the capability; product behavior remains
default-off until goal policy enables it.
The CLI is the contract authority. This skill supplies a host-neutral review workflow. Repository instructions, tests, linters, type checkers, and security checks remain the project's quality oracles.
Prepare The Exact Scope
From the repository worktree, run:
loopx --format json change-quality prepare \
--goal-id <goal-id> \
--repo-path . \
--base-ref origin/main
Stop when the packet says disabled or no_changes. When it says
review_required, review only the files and exact fingerprint in the packet.
Read repository-local instructions before judging the change.
Run loopx project-skill status --project . --skill loopx-change-quality when
the host depends on skill discovery. If the managed copy is absent or stale,
preview an explicit project install; do not fall back to a global copy.
Review Rules
Simplify First
Spend the review budget on simplification before broad quality analysis:
- Reuse an established helper or durable repository rule instead of copying behavior or knowledge.
- Remove redundant state, parameters, branches, indirection, and speculative abstraction while preserving behavior.
- Challenge a private helper or wrapper when it is only one to three lines, has at most two production callers, and owns no independent domain invariant, effect, or error boundary.
- Prefer the smallest coherent edit that leaves ownership and intent clearer. Do not create churn when the current shape is already direct and cohesive.
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.
- 1mo ago First seen · 204 lines · 75 tokens per session scan A 925963bb3ae8
loopx-change-quality is a skill published in the GitHub repository huangruiteng/loopx (6,356 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,841 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
build-review-loop
Use when the user says 'review loop N times', 'build then review', 'fix and re-review', or wants an iterative quality gate with different models building vs reviewing. Orchestrates N rounds of build-review-fix using Cursor CLI for build and Codex or another model for review.
curating-dataflow-pipeline-skills
Promote exceptionally reviewed DataFlow pipelines into reusable task-pattern skills, or update an inferior same-task skill while preserving comparison evidence and history.
taste
Cross-model code review - Codex reviews the diff read-only, then Claude validates every finding against the code before presenting it. Use when the user asks for a review, a second opinion, or a cross-model check. Offer it for large or risky diffs; invoke it directly only when the routing policy is autonomous.
refire
Turns confirmed findings from a taste into one scoped fix run, then re-verifies each finding at its cited location. Use after /sous-chef:taste when the user says to fix the findings, apply the review, or refire it. Not for new feature work - that is a fresh /sous-chef:fire.
security-code-review
Use when reviewing code for security vulnerabilities, OWASP Top 10 compliance, secure coding standards, authentication/authorization patterns, and vulnerability remediation. Includes static analysis, threat modeling integration, and security testing guidance. Based on CSSLP, CISSP certifications and OWASP standards.
anti-pattern
Anti-pattern detection and prevention skill. Catches hardcoded data, non-functional UI elements, placeholder code, N+1 queries, and other common development anti-patterns before they ship.