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-pr-programgit 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-pr-program)<a href="https://agentmods.dev/skills/huangruiteng/loopx/loopx-pr-program"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-pr-program/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-pr-program"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-pr-program.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.00095 | $0.01531 |
| Opus 5.5 | $0.00038 | $0.00612 |
| Sonnet 5.5 | $0.00019 | $0.00306 |
| Haiku 4.5 | $0.00010 | $0.00153 |
Grade A, and why
loopx-pr-program 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LoopX PR Program
Manage a delivery program as durable LoopX state instead of rebuilding a queue from chat memory. Keep source acquisition provider-local, normalize observations into one public contract, and write back only material transitions.
Route The Request
Use this workflow when the user asks to manage, prioritize, reconcile, document,
or monitor several pull requests or merge requests. Route a deep review of each
selected PR to loopx-pr-review. Route approval, comments, reruns, branch
retargeting, closing, or merging to the normal provider-specific workflow and
require the corresponding authority.
Treat document maintenance and monitor creation as writes. A request to update the roadmap or keep monitoring the program authorizes those scoped writes; an ordinary status question remains read-only.
Start From LoopX State
Start or join the project goal before material work. Represent the program with
one advancement todo for the current reconciliation and one
continuous_monitor todo for recurring observation. Do not create one monitor
todo per change request.
Use a stable monitor identity:
task_class=continuous_monitor
action_kind=pr_program_reconcile
target_key=pr-program-<stable-program-id>
cadence=<user cadence or 30m>
Preserve claimed_by, last_checked_at, next_due_at, result_hash,
consecutive_no_change, and material_change. Quiet monitor polls keep
liveness but do not count as delivery progress, rewrite roadmap documents, or
spend progress quota.
Acquire A Complete Snapshot
Use any authorized source-control read interface available in the current environment. Prefer one batch query for inventory and targeted reads for the items that changed. Never encode a private transport command, executable name, credential, internal hostname, or document token in this skill, repository examples, committed fixtures, or public evidence.
Normalize observations using
references/snapshot-contract.md. Mark
result_completeness.complete=true only after proving the requested repository,
author, state, and time-window inventory is exhaustive. An incomplete current
snapshot must not make absent rows look closed or removed.
Persist the structured scope fingerprint with the baseline. Do not advance the
durable baseline or grouped-monitor result_hash from an incomplete snapshot
or when the previous and current scope fingerprints differ; otherwise a partial
page or narrowed query can create false remove/re-add transitions on the next
poll.
What ships with it
4 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 · 164 lines · 95 tokens per session scan A feb0428eb9ef
loopx-pr-program is a skill published in the GitHub repository huangruiteng/loopx (6,233 stars, last pushed 5d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,531 once invoked, about $0.0004 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
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…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…