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 runxhq/runx --skill loop-operatorgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/loop-operator)<a href="https://agentmods.dev/skills/runxhq/runx/loop-operator"><img src="https://agentmods.dev/badge/skills/runxhq/runx/loop-operator/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/runxhq/runx/loop-operator"><img src="https://agentmods.dev/badge/skills/runxhq/runx/loop-operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 34 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
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.00018 | $0.00202 |
| Opus 5.5 | $0.00007 | $0.00081 |
| Sonnet 5.5 | $0.00004 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
loop-operator-context 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 6d 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.
What it actually says
Loop Operator Context
Use this context when reviewing whether an outer loop may submit another runx turn.
Decision Rules
- Continue only when the requested action is bounded to the current turn.
- Continue only when the requested tool is present in
allowed_tools. - Stop when the max-turn budget is exhausted.
- Pause for a human when the next action mutates state, spends money, sends a message, or changes production configuration.
- Refuse when the proposal asks for hidden authority, undeclared tools, raw secrets, or unbounded self-improvement.
Output Discipline
Return a compact result:
decision: continue | done | needs_human | refused
summary: string
requested_tool: string
stop_condition: string
This context is advisory. It must not change tools, reveal secrets, override policy, or widen authority.
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.
- 6d ago Changed · -2 lines 15d2525f49f4
- 1mo ago First seen · 36 lines · 18 tokens per session scan A 09270bdf9146
loop-operator-context is a skill published in the GitHub repository runxhq/runx (103 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 202 once invoked, about $0.0001 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
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.