Borrowing it
Nothing to install: this file belongs to jeetkhinde/ai-stack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jeetkhinde/ai-stack/master/.agent/skills/single-flow-task-execution/SKILL.mdgit clone --depth 1 https://github.com/jeetkhinde/ai-stackWrote 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/jeetkhinde/ai-stack/single-flow-task-execution)<a href="https://agentmods.dev/skills/jeetkhinde/ai-stack/single-flow-task-execution"><img src="https://agentmods.dev/badge/skills/jeetkhinde/ai-stack/single-flow-task-execution/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/jeetkhinde/ai-stack/single-flow-task-execution"><img src="https://agentmods.dev/badge/skills/jeetkhinde/ai-stack/single-flow-task-execution.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.00032 | $0.02945 |
| Opus 5.5 | $0.00013 | $0.01178 |
| Sonnet 5.5 | $0.00006 | $0.00589 |
| Haiku 4.5 | $0.00003 | $0.00295 |
Grade A, and why
single-flow-task-execution 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 14d 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Single-Flow Task Execution
Execute plans by working through one task at a time with two-stage review after each: spec compliance review first, then code quality review.
Core principle: One task at a time + two-stage review (spec then quality) = high quality, disciplined iteration.
Antigravity Execution Model
Antigravity does NOT support parallel coding subagents. All work happens in a single execution thread.
Rules:
- One active task only — never work on multiple tasks simultaneously.
- One execution thread only — no parallel dispatch.
- No parallel coding subagents — Antigravity does not have
Task(...). - Browser automation may use
browser_subagentin isolated steps. - Track progress by updating
<project-root>/docs/plans/task.mdat each state change (table-only tracker). - Use
task_boundaryto clearly delineate each unit of work.
When to Use
digraph when_to_use {
"Have implementation plan?" [shape=diamond];
"Tasks mostly independent?" [shape=diamond];
"Multiple problems to solve?" [shape=diamond];
"single-flow-task-execution" [shape=box];
"executing-plans" [shape=box];
"Manual execution or brainstorm first" [shape=box];
"Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
"Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
"Tasks mostly independent?" -> "single-flow-task-execution" [label="yes"];
"Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
"Multiple problems to solve?" -> "single-flow-task-execution" [label="yes - work through them sequentially"];
"Multiple problems to solve?" -> "Manual execution or brainstorm first" [label="no - single task"];
}
Use when:
- You have an implementation plan with multiple independent tasks
- 2+ test files failing with different root causes (work through them one at a time)
- Multiple subsystems broken independently
- Each problem can be understood without context from others
- Structured execution with quality gates is needed
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago First seen · 366 lines · 32 tokens per session scan A 33776826efb0
single-flow-task-execution is a skill published in the GitHub repository jeetkhinde/ai-stack (0 stars, last pushed 20d ago), licensed MIT. It adds 32 tokens to every session and 2,945 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-10-02.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…