yesloop

yesloop is a skill for Claude Code from carsteneu/yesmem. It costs 48 tokens per session (14,247 once invoked), scanned A, original, Apache-2.0.

An autonomous task workflow that guides an agent through analysing, planning, doing, checking, reviewing, and finishing a coding task. It runs in a separate Git worktree, an isolated copy of a repository.

In plain words
What is it for?
Running coding tasks autonomously while isolating the work, checking the result, and reporting progress through the defined workflow.
Why use it?
It keeps autonomous changes separate from your current files and adds explicit checks before the task is considered finished.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Codex.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is **Verification gates:** go test ./internal/config/... between milestones.

Good fit Running coding tasks autonomously while isolating the work, checking the result, and reporting progress through the defined workflow.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/carsteneu/yesmem
agentmods
npx agentmods add skills/carsteneu/yesmem/yesloop

Made for: Claude Code.

Wrote 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.

agentmods badge for yesloop

README.md
[![agentmods](https://agentmods.dev/badge/skills/carsteneu/yesmem/yesloop/github.svg)](https://agentmods.dev/skills/carsteneu/yesmem/yesloop)
Your own site
<a href="https://agentmods.dev/skills/carsteneu/yesmem/yesloop"><img src="https://agentmods.dev/badge/skills/carsteneu/yesmem/yesloop/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.

agentmods 80×15 button for yesloop

Your own site · 80×15
<a href="https://agentmods.dev/skills/carsteneu/yesmem/yesloop"><img src="https://agentmods.dev/badge/skills/carsteneu/yesmem/yesloop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 14,247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 8 findings, up to medium

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 →

  • medium Rogue Agent · line 6
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Excessive Agency · line 11
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Agent Snooping · line 22
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 26
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 50
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 739
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Excessive Agency · line 221
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 696
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.14247
Opus 5.5 $0.00019 $0.05699
Sonnet 5.5 $0.00010 $0.02849
Haiku 4.5 $0.00005 $0.01425

Measured 5d ago against content hash 5b17faa458ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

yesloop scanned grade A with 1 finding 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 5d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

allowed-tools: Bash(git *) Bash(go *) Bash(make *) Bash(npm *) Bash(docker *) Bash(python3 *) Bash(sqlite3 *) Bash(curl *) Bash(find *) Bash(ls *) Bash(cat *) Bash(rg *) Bash(mv *) Bash(cp *) Bash(rm *) Bash(mkdir *) Bas
skills/bundled-skills/yesloop/SKILL.md · 824 lines

How it starts

The opening of the file, as written. The whole thing — 824 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Autonomous Task Loop

You are an autonomous agent. Work through tasks without asking the user.

CRITICAL: Always spawn in a worktree

When invoked from an interactive session, do NOT execute the pipeline yourself. Instead, spawn an isolated agent in a git worktree:

  1. Create worktree: git worktree add -b yesloop/<task-slug> <repo>/.worktrees/yesloop-<task-slug>
    • Isolates agent changes from your working directory
    • Multiple agents can run in parallel without conflicts
    • Easy cleanup: delete worktree + branch if abandoned
  2. Write the task to scratchpad with worktree path and skill-read mandate: scratchpad_write(project="<project>", section="yesloop-<task-slug>", content="YOU ARE A YESLOOP-AGENT. MANDATORY - YOU MUST READ THE YESLOOP SKILL AND YOU MUST FOLLOW THE INSTRUCTIONS IN THIS SKILL. Load the yesloop skill: use your platform's skill tool, or read ~/.claude/skills/yesloop/SKILL.md, or <repo-root>/skills/bundled-skills/yesloop/SKILL.md. Follow the 6-phase pipeline (ANALYZE → PLAN → EXECUTE → VERIFY → REVIEW → FINISH) FORMALLY AND SUBSTANTIVELY with ATTENTION.\n\nWorktree: <path>\nTask: <description>\nSession title: <one-line title from the requirement, max ~60 chars>\n\nReport to scratchpad.") The spawned agent has NOT auto-loaded this skill — the mandate prefix is mandatory.
  3. Spawn TUI agent (MANDATORY — never run the pipeline inline): yesmem_spawn_agent(project="<project>", section="yesloop-<task-slug>", backend="opencode", work_dir="<worktree-path>")
  4. Wait 15s for opencode TUI to load + PTY injection to deliver the startup prompt
  5. Relay kick (backup): yesmem_relay_agent(to="<agent-id>", content="Read scratchpad section 'yesloop-<task-slug>' AND load the yesloop skill (skill tool or ~/.claude/skills/yesloop/SKILL.md). MANDATORY - YOU MUST READ THE YESLOOP SKILL AND YOU MUST FOLLOW THE INSTRUCTIONS IN THIS SKILL. Your agent id: <agent-id>. At Phase 1 start, rename your session to '[<agent-id>] <Session title from briefing>'. Begin the 6-phase pipeline FORMALLY AND SUBSTANTIVELY with ATTENTION.\n") — backup if PTY is slow
  6. Confirm: "Agent spawned in worktree — visible in terminal."

Read the full file on GitHub · 824 lines

Changes

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.

  1. 5d ago Changed · +4 lines 5b17faa458ce
  2. 19d ago Changed · +39 lines 39cb0c707927
  3. 1mo ago Changed · +67 lines 1ec02d260750
  4. 1mo ago First seen · 714 lines · 48 tokens per session scan A 66c0725bc506

Subscribe to this mod's changes

yesloop is a skill published in the GitHub repository carsteneu/yesmem (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 48 tokens to every session and 14,247 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

pre-pr

Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.

plastic-labs/honcho · 69 tokens

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

thedotmack/claude-mem · 44 tokens

pr-reviewer

Fetches PR review comments, analyzes requested changes, implements fixes, commits and pushes the resolution. Use after a reviewer has left comments on an open PR to close the feedback loop efficiently.

Fu-Jie/openwebui-extensions · 41 tokens

mulch-record-from-evidence

Turn the evidence of a finished work session — git commits, changed files, recently-touched seeds issues — into well-formed ml record invocations. Use at session close, when an agent has made changes worth preserving as mulch expertise but hasn't yet recorded them.

jayminwest/mulch · 61 tokens

github

Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".

diillson/chatcli · 78 tokens

dos-verify-done-claims

Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.

anthony-chaudhary/dos-kernel · 61 tokens