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-projectgit 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-project)<a href="https://agentmods.dev/skills/huangruiteng/loopx/loopx-project"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-project/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-project"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 91 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 493 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00074 | $0.11776 |
| Opus 5.5 | $0.00030 | $0.04710 |
| Sonnet 5.5 | $0.00015 | $0.02355 |
| Haiku 4.5 | $0.00007 | $0.01178 |
Grade A, and why
loopx-project 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 — 1,084 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LoopX Project Workflow
Use this skill when the task mentions LoopX, loopx, a project goal
document, multi-project dashboard/status, stale latest run,
.loopx/registry.json, .codex/goals, refresh-state,
sync-global, or connecting a new repo. If the task is mainly about reading,
remembering, recording, indexing, or registering a durable project material,
load loopx-doc-registry and use that narrower workflow first.
LoopX has two layers:
- Project-local state: each repo owns
.loopx/registry.jsonand.codex/goals/<goal-id>/ACTIVE_GOAL_STATE.md. - Shared local control plane:
~/.codex/loopxstores run history andregistry.global.jsonfor multi-project status.
Do not manually copy one project's registry entry into another project. Local
connect and refresh-state should sync into the shared global registry
automatically.
Slash Command Fallback
When asked to upgrade LoopX on a machine with the desktop App, inspect the App
bundle and its runtime as well as the CLI. loopx doctor exposes
desktop_installation for standard macOS install locations; a paired bundle
still does not prove which App process is running. Upgrade the App and its
bundled runtime together, then restart and verify the App, CLI and service
source revisions. Never claim a desktop upgrade from CLI/HTTP checks alone:
current App builds ask before replacing a different CLI runtime (update the
App, or align the CLI to the App's bundled runtime), while an older build can
still replace a separately upgraded CLI with its bundle.
Keep SSH host verification separate; a host without an App needs no App install.
When the visible user message is exactly a LoopX slash command or starts with a LoopX slash command plus arguments, do not treat it as ordinary chat.
Recognized project-local goal-start command:
/loopx <goal text>/loopx --capability-route issue-fix <goal text>
Recognized repo-review commands:
/loopx-pr-review/loopx-pr-review <time window or filter text>
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 Changed · +2 lines 2ab0d722e707
- 1mo ago Changed · +1 lines 455556e62551
- 1mo ago Changed · -21 lines 55cdc2976930
- 1mo ago Changed · +39 lines f304da7e943b
- 1mo ago Changed · +14 lines fb140e37cccd
- 1mo ago First seen · 1,049 lines · 74 tokens per session scan A 1d5de3416c86
loopx-project is a skill published in the GitHub repository huangruiteng/loopx (6,356 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 11,776 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
b3os-team-inbox
A team message-bus client for sending, receiving, and recalling messages between AI teammates. It also supports replying to a specific message thread and sending final reports to the team lead.
b3os-task-loop
A task-tracking work loop that keeps individual, scheduled, and waiting tasks moving until they are completed, blocked, or awaiting approval.
b3os-sf
A software-development method for turning a growing list of team requests into planned, reviewed, tested, documented, and released work. It describes a project structure with a repository, design notes, task tracking, continuous integration, and agent collaboration.
b3os-task-mgmt
A deprecated compatibility stub that points users to b3os-task-loop, the newer source for task boards, execution mode, handoffs, continuation checks, review waiting, and scheduled work.
github-loop-engineering-skill
Run an evidence-gated Loop Engineering control loop for GitHub Issues and GitHub Projects through the official GitHub MCP Server, keeping every issue cold-startable for a new collaborator or a fresh agent session. Use when an agent needs to discover work state; create, triage, prioritize, assign, split, block, start…
agile-project-management
Use when managing agile projects, facilitating Scrum ceremonies, conducting backlog grooming, sprint planning, velocity tracking, and implementing Kanban workflows. Includes agile metrics, team dynamics, and agile transformation guidance. Based on CSM, CSP, PRINCE2 certifications.