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/worker_skillnpx skills add huangruiteng/loopx --skill worker_skillgit 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.00079 | $0.03062 |
| Opus 5 | $0.00039 | $0.01531 |
| Sonnet 5 | $0.00016 | $0.00612 |
| Haiku 4.5 | $0.00008 | $0.00306 |
Grade A, and why
loopx-auto-research 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LoopX Auto Research
This is a worker-local role playbook for auto-research panes. It is packaged with the auto-research capability and should be injected or referenced by the worker launcher; it is not a global LoopX skill for ordinary project agents.
Routing Boundary
Use this skill after a LoopX auto-research worker has a role profile, frontier item, launcher packet, or user-visible demo pane. The skill is the role playbook. It is not the source of truth for identity, authority, current frontier, or merge/publication permission.
Identity comes from LoopX control-plane metadata:
auto_research_role_profile_v0in the launcher/frontier/bootstrap packet;quota should-run --goal-id ... --agent-id ...;- todo claim, capability token, write scope, and protected scope;
- repository or workspace
AGENTS.mdrules, which can only make the boundary stricter.
No role owns the full graph. Do not infer role from pane title, branch name, tmux window name, or the section of this skill that happens to be visible.
Pane Tick Contract
The generic multi-agent kernel owns the default LoopX project/doc-registry skills and the fixed A2A wake prompt. This skill should stay role-specific: use it after the pane-local tick has resolved identity, quota, and frontier from LoopX.
Compact frontier command: loopx --format json auto-research frontier --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID". Also honor quota should-run.
If the launcher exported LOOPX_ROLE_ID, LOOPX_ROLE_PROFILE_REF, or a profile
JSON path, compare those values with the quota and frontier packets. Stop when
they disagree. Do not guess the intended role.
If the role profile includes successor_todos, treat those declarations as the
only role-local way to create the next agent todo. A successor declaration must
name the target agent and include a todo_command_template such as
loopx todo add ... --claimed-by {target_agent_id_shell}. In visible
auto-research, the pane-local tick is a guard/frontier read, not a research
writer. Render and run a successor todo only after the visible role has authored
real public-safe evidence or notes that satisfy the declared condition. Do not
invent an extra continuation plan in prose, and do not ask a leader pane to pick
the next role.
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 · 360 lines · 79 tokens per session scan A db1a1ad11155
loopx-auto-research is a skill published in the GitHub repository huangruiteng/loopx (5,394 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 3,062 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.
skill-maintainer
Track upstream drift and sync adapted skill libraries.
create-workflows
Creates and revises portable declarative AI workflow files using Markdown frontmatter, DAG nodes, provider IDs, artifact references, imports, reusable inputs, findings artifacts, and review loops. Use when asked to author, improve, modularize, or validate .task.md workflows for CLI-based multi-agent workflow…
claude-plugin-converter
Convert Claude Code plugins into self-contained Hermes plugins — discovery analysis then full conversion.
input-token-overheads
Use when context window is filling up too fast or input token cost is too high. Audits overhead sources.
skill-retrieval
BM25-based skill retrieval plugin for Hermes Agent. Replaces the full skill list in the system prompt with a names-only compact view (2K tokens) and injects top-K relevant skill descriptions per turn via BM25 retrieval (300 tokens). Saves 9K tokens/turn. Use when system prompt token overhead from skills is a concern…