What is auto_task.execute_interactively?

A workflow that executes an ordered task list by alternating coding-agent work, human review, and commits in one branch. It also creates the GitHub issue, branch, and draft pull request before starting.

Use it for sequential development tasks that need a local review loop and should not be committed or merged automatically.

It provides checkpoints for people to review each task and keeps committing and merging under human control.

auto_task.execute_interactively — Skill for Claude Code by gpsaggese

Install

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.

Any agent

npx skills add gpsaggese/helpers --skill auto_task.execute_interactively

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.execute_interactively/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/auto_task.execute_interactively)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/auto_task.execute_interactively"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.execute_interactively/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gpsaggese/helpers/auto_task.execute_interactively"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.execute_interactively.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,034 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.01034
Opus 5.5	$0.00006	$0.00414
Sonnet 5.5	$0.00003	$0.00207
Haiku 4.5	$0.00002	$0.00103

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

Security

Grade A, and why

auto_task.execute_interactively 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 yesterday.

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.

.claude/skills/auto_task.execute_interactively/SKILL.md · 102 lines

How it starts

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

Goal

Execute an ordered list of well-specified, sequential tasks <FILE> by alternating agent execution, human review, and commit in a branch
Create the GH issue, branch, and PR for <FILE> before the loop: each auto_task maps to one GH issue and one branch/PR (see .claude/skills/auto_task.rules.md)
Follow .claude/skills/auto_task.rules.md for how tasks are queued, specified, and named

When to Use This Skill

Follow .claude/skills/auto_task.rules.md section "Ask for Clarification Before Executing an Unclear Plan" when a task's spec is unclear or incomplete

Conventions

Follow .claude/skills/auto_task.rules.md for queue, spec, naming, and coding/testing conventions

Constraints

Create the GH issue, branch, and (draft) PR for <FILE> up front: this is this skill's job, not the user's
Do not commit any code change for a task: committing is the user's decision
Do not merge any PR: merging is the user's decision

Workflow

Confirm the Task List

Read <FILE> and follow .claude/skills/auto_task.rules.md section "Confirm the Task List Before Executing" for the format and the problem/solution check
Make sure each task is clear. Add a plan of 5 markdown bullets under each task
If the order or a dependency is unclear, follow the "Ask for Clarification Before Executing an Unclear Plan" section of .claude/skills/auto_task.rules.md before starting

Create the Issue and the Branch

Follow .claude/skills/auto_task.rules.md section "One GitHub Issue Is the Unit of Work": one GH issue covers the whole task list in <FILE>
Create the issue and branch (<RepoPrefix>Task<IssueNum>_<Description>) in one shot with git_create_issue_and_branch.py. Unlike invoke gh_issue_create and invoke git_branch_create, it also branches submodules (e.g., helpers_root)
```
> git_create_issue_and_branch.py \
    --gh_issue_title "<TITLE>" --gh_issue_body "<Description of the task list>" \
    --no_create_pr
```

Read the full file on GitHub · 102 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.

yesterday First seen · 102 lines · 15 tokens per session scan A d8466b232162

Subscribe to this mod's changes

auto_task.execute_interactively is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 1,034 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-11-06.

Git and workflow Project management

auto_task.execute_interactively next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
auto_task.execute_interactivelygpsaggese/helpers	Skill	158	today	Apache-2.0	A	15	Claude Code
merge-batchdiegosouzapw/OmniRoute	Skill	83k	6d ago	MIT	A	46	Claude Code
prowler-commitprowler-cloud/prowler	Skill	15k	today	Apache-2.0	A	44	Claude Code, Codex
gh-auth-isolationgithub/gh-aw	Skill	5.6k	today	MIT	A	20	Claude Code, Codex
comet-githubrpamis/comet	Skill	3.3k	yesterday	MIT	A	72	Claude Code, Codex
github-skillzeenie-ai/OpenCompany	Skill	1.1k	2d ago	MIT	A	51	Claude Code
release-helperSahir619/fable-method	Skill	2.3k	1mo ago	MIT	A	43	Claude Code