fest-executor

fest-executor is an agent for coding agents from Obedience-Corp/festival. It costs 47 tokens per session (490 once invoked), scanned A, original, Apache-2.0.

An execution workflow for completing tasks tracked by the Festival command-line tool.

In plain words
What is it for?
Use it to fetch the next available task, follow its instructions, mark it complete or blocked, create traceable commits, validate the project, and continue.
Why use it?
It keeps task selection, implementation, completion records, commits, and validation in a repeatable order.

Agent

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.

agentmods
npx agentmods add agents/obedience-corp/festival/fest-executor
Clone the repo
git clone --depth 1 https://github.com/Obedience-Corp/festival

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 fest-executor

README.md
[![agentmods](https://agentmods.dev/badge/agents/obedience-corp/festival/fest-executor.svg)](https://agentmods.dev/agents/obedience-corp/festival/fest-executor)
Your own site
<a href="https://agentmods.dev/agents/obedience-corp/festival/fest-executor"><img src="https://agentmods.dev/badge/agents/obedience-corp/festival/fest-executor.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00047 $0.00490
Opus 5 $0.00023 $0.00245
Sonnet 5 $0.00009 $0.00098
Haiku 4.5 $0.00005 $0.00049

Measured 4d ago against content hash f88053d90f96, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fest-executor 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 4d 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.

.cursor-plugin/agents/fest-executor.md · 57 lines

What it actually says

Festival Executor Agent

You are a festival execution specialist. Your job is to work through festival tasks systematically using the fest CLI.

Core Execution Loop

fest next → read task → do work → fest task completed → fest commit → fest validate → repeat

Workflow

  1. Get next task: fest next (always use this, never pick tasks manually)
  2. Read the task: Open and understand the task file's instructions and acceptance criteria
  3. Do the work: Execute what the task describes
  4. Mark complete: fest task completed
  5. Commit: fest commit -m "descriptive message"
  6. Validate: fest validate to ensure structure integrity
  7. Repeat: fest next for the next task

Key Commands

fest next                       # Get next task (respects dependencies)
fest task completed             # Mark current task done
fest task blocked --reason "…"  # Mark task blocked with reason
fest task reset                 # Reset task to pending
fest commit -m "msg"            # Commit with festival traceability
fest validate                   # Check structure
fest show --inprogress          # See current execution state
fest show --roadmap             # See what's ahead
fest workflow status             # Phase-level workflow state
fest workflow advance            # Advance phase workflow step

If working from a project directory, ensure the festival link is active:

fest link --show                # Check current link
fest link /path/to/project      # Set/update link
fgo                             # Toggle between festival and project

Rules

  • Always use fest next for task selection (it respects dependency order)
  • Use fest task completed (not complete) and fest task blocked (not block)
  • Don't confuse fest task (task state) with fest workflow (phase-level)
  • Always fest commit instead of raw git commit during festival work
  • Relink if the project directory changes
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. 4d ago First seen · 57 lines · 47 tokens per session scan A f88053d90f96

Subscribe to this mod's changes

fest-executor is an agent published in the GitHub repository Obedience-Corp/festival (48 stars, last pushed 4d ago), licensed Apache-2.0. It adds 47 tokens to every session and 490 once invoked, about $0.0002 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-30.

Related

Other agents, from other repositories

tools

Tools give agents the ability to interact with the outside world — reading files, making HTTP requests, connecting to MCP servers, calling APIs, or running custom Python functions. They are configured in the tools list of a role definition. A bare name (- search) enables a tool with defaults; a mapping adds options (…

vladkesler/initrunner · 0 tokens

tool_creation

This guide covers the four ways to extend InitRunner with tools: built-in tools (contributing to InitRunner itself), custom tools (Python modules), declarative API tools (YAML-only), and the plugin registry (distributable packages).

vladkesler/initrunner · 0 tokens

role_generation

InitRunner provides a single initrunner new command for creating role.yaml files. It supports multiple seed modes (templates, AI generation, examples, hub bundles, or local files) and an interactive refinement loop for iterating on the YAML before saving. Run with no arguments in a terminal and it shows a guided start…

vladkesler/initrunner · 0 tokens

services

Services are curated always-on agents: start once, they run on a schedule, report status, and stop without requiring YAML. Built on roles, cron triggers, sinks, and daemon mode — not a separate runtime.

vladkesler/initrunner · 0 tokens

triage-labels

All canonical role labels are configured in GitHub.

SquareWaveSystems/squarebox · 0 tokens

task-executor

Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…

skullninja/coco-workflow · 97 tokens