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 agentmods add skills/huangruiteng/loopx/loopx-projectnpx skills add huangruiteng/loopx --skill loopx-projectgit clone --depth 1 https://github.com/huangruiteng/loopxWhat 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 | $0.00074 | $0.11137 |
| Opus 5 | $0.00037 | $0.05568 |
| Sonnet 5 | $0.00015 | $0.02227 |
| Haiku 4.5 | $0.00007 | $0.01114 |
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 2d 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,049 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 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>
If the text after /loopx begins with the exact optional prefix
--capability-route issue-fix, remove only that prefix from the goal text and
pass it as the explicit start-goal route switch. Otherwise every non-whitespace
character after /loopx is goal text. Never infer a product capability route
from issue/PR wording, URLs, or semantic similarity. Do not downgrade either
form into a status or inspection turn.
start-goal --project keeps the requested project route, including a linked
git worktree, so a fresh task cannot inherit an older worktree's goal.
Lower-level diagnostic command packs may still report a canonical
canonical_project_alias / source_registry route. Do not manually replace
either route with an unadvertised bootstrap command.
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.
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.
- 2d 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 (5,394 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 11,137 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-30.
Other skills, from other repositories
agent-onboarding
Onboard yourself to a repo where several agents work in parallel, syncing through a shared TODO.md. Use when joining the team on a shared codebase.
context-chain
세션 간 맥락을 연결해야 할 때. — MUST TRIGGER: 세션 시작 시 NOVA-STATE.md 읽기, 커밋 후 상태 갱신, 스프린트 전환 시.
status-dashboard
프로젝트 현황(Phase·Sprint·그룹 진행률) + 로드맵 drift 알람을 stand-alone HTML로 본다. — MUST TRIGGER: /nova:status 호출, 사용자가 '현황 보여줘'·'어디까지 됐어'·'drift 확인' 요청 시, AI 위임 후 결과 점검 필요할 때. 자율 우회 금지 — 프로젝트 자체 dashboard 도구·NOVA-STATE 텍스트 요약으로 대체 행위 차단.
loop-build
(loop-engineering) Implements exactly one feature from the BACKLOG.md Backlog — syncs main, acquires the loop lock, creates a feature branch, implements all acceptance criteria with tests, visually inspects UI changes, passes the independent verifier, and opens a PR. Use for Build-mode loop runs, or when asked to…
loop-report
(loop-engineering) Runs the daily Report-mode triage — checks open PRs, CI status and the BACKLOG.md backlog, then updates STATE.md and appends to the run log without writing any code. Use for scheduled daily loop runs, project health checks, or when asked to "triage", "run report mode", or "update the loop state".
github-loop-engineering-skill
Run an evidence-gated Loop Engineering control loop for GitHub Issues and GitHub Projects through the official GitHub MCP Server. Use when an agent needs to discover work state; create, triage, prioritize, assign, split, block, start, finish, close, or verify work items; update project fields; maintain acceptance…