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 ulises-jeremias/agent-toolkit --skill loop-runnergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/loop-runner)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/loop-runner"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/loop-runner/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/ulises-jeremias/agent-toolkit/loop-runner"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/loop-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00882 |
| Opus 5.5 | $0.00013 | $0.00353 |
| Sonnet 5.5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
loop-runner 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-runner
Execute and manage loop engineering primitives from an AI coding session.
What this skill does
This skill wraps the agent-toolkit loop CLI (V product command), exposing loop
operations to AI coding agents without requiring the user to remember CLI flags.
Loop engineering is the practice of designing recursive, autonomous processes
that prompt AI agents — as opposed to prompting agents directly. Loops have
durable state (STATE.md), safety gates (allowlist/deny), cost budgets, and
rollout tiers (L1 report-only → L2 PR-gated → L3 unattended).
Capabilities
| Subcommand | When to use |
|---|---|
loop init <pattern> |
Scaffold a new loop from a starter |
loop run <loop> |
Execute one loop iteration |
loop status |
Show all loops: tier, cadence, last run |
loop audit [loop] |
Summarize past run success/cost |
loop cost <loop> |
Estimate per-run token cost |
loop schedule <loop> |
Install systemd/launchd timer |
loop sync |
Push escalations to knowledge/todos |
How to invoke
# Preferred — agent-toolkit V CLI
agent-toolkit loop status
agent-toolkit loop run daily-triage
agent-toolkit loop init oss-pr-monitor
Historical note: older docs referred to ./bin/loop or ~/.ai-workspace/bin/loop.
Those entrypoints are obsolete; use agent-toolkit loop after installing via
brew / AUR agent-toolkit-bin / GitHub Release / uv tool install agent-toolkit-cli.
Routing
- Prefer
agent-toolkit loop …on PATH (V binary or PyPI launcher) - Otherwise guide the user to install per
docs/INSTALLATION.md
Runner hierarchy
When agent-toolkit loop run dispatches a loop, it tries runners in this order:
| Priority | Runner | How to enable |
|---|---|---|
| 1 | runner | export HARNESS_RUNNER_DIR="$HOME/.local/share/agentic-workstation/dev-companion/runner" |
| 2 | claude --print (Claude Code CLI) |
claude in PATH — zero setup for Claude Code users |
| 3 | Skeleton plan | Always available |
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.
- 1mo ago First seen · 95 lines · 32 tokens per session scan A 6491c61915a1
loop-runner is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 882 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-09-04.
Other skills, from other repositories
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
audit-accomplishments
Use when preparing a performance self-reflection, midyear or annual review, promotion packet, or brag document; when asked to collect, mine, gather, or summarize your accomplishments, contributions, or impact over a period; or when assembling cited evidence of work done across GitHub, Jira, Notion, Slack, and local…
start-day
Use at the start of a workday or when the user says "start my day", "good morning", "/start-day", "morning", "what should I work on today", or wants a catch-up on what happened while they were away. Use when the user wants a short ranked list of what to tackle today.
tracking-time
Tracks time on tasks using timers or manual entries and generates timesheet reports in Astravue. Use when logging work hours, starting or stopping a timer, reviewing time entries, generating timesheets, or asking "how much time was spent on this?".
local-mcp-daily-brief
Use when the user asks "what's on my plate today", "catch me up", "morning brief", or wants a summary of their day across calendar, reminders and email. The single most common multi-step automation. Powered by LMCP on macOS and Windows.
local-mcp-email-to-action
Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.