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 mekotenkov-ux/seomeatagentscreator --skill workflow-loop-megit clone --depth 1 https://github.com/mekotenkov-ux/seomeatagentscreatorWrote 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/mekotenkov-ux/seomeatagentscreator/workflow-loop-me)<a href="https://agentmods.dev/skills/mekotenkov-ux/seomeatagentscreator/workflow-loop-me"><img src="https://agentmods.dev/badge/skills/mekotenkov-ux/seomeatagentscreator/workflow-loop-me/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/mekotenkov-ux/seomeatagentscreator/workflow-loop-me"><img src="https://agentmods.dev/badge/skills/mekotenkov-ux/seomeatagentscreator/workflow-loop-me.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.01143 |
| Opus 5 | $0.00030 | $0.00571 |
| Sonnet 5 | $0.00012 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
workflow-loop-me 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Loop Me
Задача - не просто понять, какого агента хочет пользователь, а выяснить, какие повторяемые рабочие процессы реально стоит делегировать агенту.
Используйте после grill-me и до архитектуры агента.
Prior art: loop/workflow lens вдохновлен открытым MIT skill loop-me by Matt Pocock: https://github.com/mattpocock/skills/blob/main/skills/in-progress/loop-me/SKILL.md
Главный принцип
Ищите loops: повторяемые паттерны в работе пользователя, команды, недели, дня, канала, inbox, issue flow, продажах, контенте, QA, исследованиях, отчетности или поддержке.
Workflow - это спецификация одного loop, которую можно реализовать как агентский процесс, обычный checklist, automation, tool run или гибрид. Не навязывайте AI, расписание, checkpoint или автономию, если интервью не доказало, что они нужны.
Правила интервью
- Задавайте один материальный вопрос за раз.
- Для каждого вопроса давайте recommended default, если он уместен.
- Не превращайте разговор в длинную анкету.
- Сначала ищите существующие артефакты: docs, tickets, reports, scripts, spreadsheets, inbox labels, calendars, SOPs, dashboards, logs.
- Записывайте язык пользователя: как он сам называет каналы, события, роли, артефакты и проблемы.
- Не проектируйте агента, пока ключевой workflow не описан как реализуемая спецификация.
Vocabulary
Используйте эти термины только когда они помогают уточнить процесс:
- Loop - повторяемая активность или ситуация.
- Workflow spec - документированная версия loop, пригодная для реализации.
- Trigger - событие или расписание, которое запускает run.
- Input - что приходит на вход: файл, issue, письмо, чат, URL, таблица, запрос, сигнал.
- Actor - кто участвует: пользователь, клиент, reviewer, agent, tool, external system.
- Tool/channel - где workflow живет: repo, CRM, docs, messenger, inbox, dashboard, IDE, CMS.
- State - что нужно помнить между runs.
- Artifact - что workflow создает или меняет.
- Checkpoint - где человек должен принять решение или проверить результат.
- Brief - короткая decision-ready выжимка для checkpoint, а не raw draft.
- Push right - отложить checkpoint как можно дальше, чтобы человек видел уже подготовленное решение.
- Done signal - внешний признак, что run завершен.
- Failure mode - как workflow ломается и что делать.
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.
- 9d ago First seen · 88 lines · 59 tokens per session scan A aebcf54a8609
workflow-loop-me is a skill published in the GitHub repository mekotenkov-ux/seomeatagentscreator (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,143 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…