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 agents/yaomeng1749/claude-code-digital-nomad-config-pack/loop-operatorgit clone --depth 1 https://github.com/Yaomeng1749/claude-code-digital-nomad-config-packWrote 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/agents/yaomeng1749/claude-code-digital-nomad-config-pack/loop-operator)<a href="https://agentmods.dev/agents/yaomeng1749/claude-code-digital-nomad-config-pack/loop-operator"><img src="https://agentmods.dev/badge/agents/yaomeng1749/claude-code-digital-nomad-config-pack/loop-operator.svg" alt="Measured on agentmods" height="20"></a>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.00019 | $0.00196 |
| Opus 5 | $0.00010 | $0.00098 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
loop-operator 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 37 lines · 19 tokens per session scan A 1a2b9c6cd104
loop-operator is an agent published in the GitHub repository Yaomeng1749/claude-code-digital-nomad-config-pack (4 stars, last pushed 4mo ago), with no licence file. It adds 19 tokens to every session and 196 once invoked, about $0.0001 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-31.
Other agents, from other repositories
verify
Traces a small set of candidate sites end to end and classifies each against a vulnerability class with evidence. Dispatched by websec detection skills during their verification phase; it decides, and it must show why.
reviewer
Adversarial reviewer of finished manuscripts. Refuses to sign off on central result claims until publication-critical metrics trace back to pinned evidence (empirical checklist) AND theorem claims trace back to an empty diagnostic manifest plus either a Lean verification or an explicit unverified flag (proof…
verifier
Independent verification of claims. Read-only access to code; can run verification tools but cannot edit.
researcher
Read-only literature review, idea generation, and hypothesis proposal. Cannot modify code or files.
planner
Decide the approach before any code changes. Produce a concrete, bounded plan.
reviewer
Validate correctness, regressions, architecture fit, and missing tests.