What is loopx-doc-registry?

A project document registry process for recording durable materials—such as design documents, research notes, procedures, and reports—so future agents can find them from the project's authoritative records.

Use it to locate the project registry, record a material source with a redacted description, and refresh project status so agents can discover it.

It prevents important project knowledge from staying only in chat or personal memory and helps keep registrations tied to the correct project.

loopx-doc-registry — Skill for Claude Code and Codex by huangruiteng: A project document registry process for recording durable materials

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/huangruiteng/loopx/loopx-doc-registry

Any agent

npx skills add huangruiteng/loopx --skill loopx-doc-registry

Clone the repo

git clone --depth 1 https://github.com/huangruiteng/loopx

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-doc-registry.svg)](https://agentmods.dev/skills/huangruiteng/loopx/loopx-doc-registry)

Your own site

<a href="https://agentmods.dev/skills/huangruiteng/loopx/loopx-doc-registry"><img src="https://agentmods.dev/badge/skills/huangruiteng/loopx/loopx-doc-registry.svg" alt="Measured on agentmods" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 645 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.

Model	Per session	Once invoked
Fable 5	$0.00074	$0.00645
Opus 5	$0.00037	$0.00322
Sonnet 5	$0.00015	$0.00129
Haiku 4.5	$0.00007	$0.00064

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

Security

Grade A, and why

loopx-doc-registry 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 4d 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.

skills/loopx-doc-registry/SKILL.md · 67 lines

How it starts

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

LoopX Doc Registry

Use this skill for durable project materials. The goal is to make future agents find the material from the project authority surface, not only from chat or personal memory.

Default Route

Resolve the target project and stable goal_id from the current repo or the user's named project. Prefer .loopx/registry.json and .codex/goals/<goal-id>/ACTIVE_GOAL_STATE.md.
If the material belongs to that project, register it in that project's own authority surface. Do not register it into loopx-meta just because the current worker discovered it.
If the project has a tracked docs/meta/DOC_REGISTRY.yaml or equivalent, update that first. If it does not, use .loopx/registry.json as the project-local doc registry through authority_registry.topic_authority and authority_registry.project_materials.
Run loopx register-authority-source with a redacted source contract. Raw URLs, doc ids, local private paths, comments, and source bodies must not be stored in public files.
Refresh status or state so review packets, read-only maps, dashboards, and heartbeat workers can find the material.

Memory extensions are allowed only as secondary personal reminders. They are not a substitute for project-local authority registration when the project is connected to LoopX.

Command Shape

From the target project:

loopx --registry .loopx/registry.json register-authority-source \
  --goal-id <goal-id> \
  --source-id <stable-source-id> \
  --source-ref "<raw-url-or-private-path-to-hash>" \
  --source-kind <doc|lark_doc|wiki|paper|owner_packet|migration_report> \
  --role <public-safe-role> \
  --freshness <current|historical|unknown> \
  --owner-status <public-safe-owner-status> \
  --gate-status <readable|needs_access|owner_review_pending> \
  --boundary private_redacted \
  --revision "<public-safe-revision-label>" \
  --conflict-rule "<public-safe-conflict-rule>" \
  --topic <topic-key>

Use --dry-run first when the source classification or target project is not obvious.

Read the full file on GitHub · 67 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.

agents/openai.yaml 259 B

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.

4d ago First seen · 67 lines · 74 tokens per session scan A c5ad255cab5c

Subscribe to this mod's changes

loopx-doc-registry is a skill published in the GitHub repository huangruiteng/loopx (5,548 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 645 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.

Planning Research agent-control-plane agent-ops ai-agents codex loop-engineering loopx

deep-research

Autonomous multi-step deep research engine implementing an iterative Think → Search → Extract → Synthesize → Stop loop. The LLM drives every decision: what to search, what's relevant, what's missing, and when to stop. Produces a cited, magazine-quality report with inline citations, category- specific formatting, and…

moonlight-lupin/agent-skills · 147 tokens

image-studio

Generate, edit and upscale AI images via fal.ai through a three-stage studio workflow — brainstorm a strong prompt with the user, prototype cheaply and iterate on feedback, then produce a finalised image. Use when the user wants image generation or editing through the local fal.ai helper workflow, including requests…

moonlight-lupin/agent-skills · 214 tokens

website-scraping

Generic playbook for extracting structured data from any website — hotel prices, flight fares, e-commerce listings, real estate, jobs, competitor product catalogues, anything where the goal is to turn one or more URLs into clean records on disk. Use this skill whenever the user mentions scraping, harvesting…

moonlight-lupin/agent-skills · 210 tokens

loopx-doc-registry