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 saski/arnesto --skill loopgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/loop)<a href="https://agentmods.dev/skills/saski/arnesto/loop"><img src="https://agentmods.dev/badge/skills/saski/arnesto/loop.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.1 | $0.00028 | $0.01755 |
| Opus 5 | $0.00014 | $0.00877 |
| Sonnet 5 | $0.00006 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
loop 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loop
Run /loop on a recurring or variable interval. First decide which mechanism applies from the tools you have, then follow only that section below:
- If the
cursor-subscriptions-subscribe_timerMCP tool is available (you are a Cloud Agent), use Subscription timer (cloud). A localsleeploop does not work in cloud. - Otherwise (local IDE/CLI session), use Monitored shell output (local).
Parse
Accept /loop [interval] <prompt>.
- Leading interval:
5m /foo,30s check status,2h run report. - Trailing interval:
check deploy every 5m,run tests every 10 minutes. - No interval: dynamic mode; the agent chooses the delay and may change it tick to tick.
- Empty prompt: show
Usage: /loop [interval] <prompt>.
Use intervals like 30s, 5m, 2h, 1d. Convert unit words to short units. If the user gives a cron-style phrase ("every weekday at 9am") and the subscription-timer mechanism is in use, pass it as a cron expression instead of a delay.
Subscription timer (cloud)
Use the cursor-subscriptions MCP timer to wake this Cloud Agent on a recurring schedule using cursor-subscriptions-subscribe_timer.
Schedule
Call cursor-subscriptions-subscribe_timer with:
name: a stable handle, e.g.loop-<purpose>derived from the prompt (loop-check-deploy). The server dedupes by name and silently keeps the old config on a dedupe hit — see "Changing an existing timer" below.prompt: the literal follow-up text the agent should receive on each tick.- Exactly one of
delaySeconds(a positive integer, fixed interval between fires) orcron(a cron expression).
Run the prompt once immediately so the first server tick is not a cold start. Then subscribe and confirm: the interval, that the prompt already ran once, the returned subscriptionId, and that the loop will fire on each tick until stopped.
Each subsequent tick arrives as a normal follow-up prompt. Do not arm anything client-side; the server keeps firing until you unsubscribe or the timer expires.
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 · 123 lines · 28 tokens per session scan A fa195d01ca95
loop is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 28 tokens to every session and 1,755 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-09-03.
Other skills, from other repositories
orbit-general
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the…
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
discovery-question-form
Structured clarification form for unresolved material requirements.
mailbox
A guide for performing email and mailbox tasks through the QwenPaw mailbox system. It covers supported personal email providers, credentials, configuration, and the required mailbox workflow.
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
ask-matt
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.