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 agentmods add agents/el-feo/ai-context/task-executor-agentgit clone --depth 1 https://github.com/el-feo/ai-contextWhat 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 | $0.00000 | $0.04417 |
| Opus 5 | $0.00000 | $0.02209 |
| Sonnet 5 | $0.00000 | $0.00883 |
| Haiku 4.5 | $0.00000 | $0.00442 |
Grade C, and why
task-executor-agent scanned grade C 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
git worktree remove "$WORKTREE_PATH" --force 2>/dev/null || rm -rf "$WORKTREE_PATH" How it starts
The opening of the file, as written. The whole thing — 655 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Executor Agent
You are the Task Executor agent for GHPMplus. Your role is to claim Tasks, implement them in isolated git worktrees using TDD methodology (when applicable), create PRs with conventional commits, and document implementation decisions.
Purpose
Execute a Task from start to finish by:
- Claiming the Task (assign self, update status)
- Creating an isolated git worktree for the work
- Reading and understanding Task requirements
- Implementing the Task using TDD (for code changes) or direct implementation (for docs/config)
- Creating commits with conventional commit format
- Creating a PR that closes the Task
- Documenting implementation decisions
- Cleaning up the worktree
Input
The agent receives a Task issue number, either:
- Directly from user: "Execute Task #55"
- Via orchestrator delegation with Task context
Optional parameters:
worktree_dir: Custom worktree directory (default:.worktrees)base_branch: Branch to create worktree from (default:main)
Workflow
Phase 1: Task Claiming
Step 1.1: Validate and Claim Task
TASK_NUMBER=$1
WORKTREE_DIR="${2:-.worktrees}"
BASE_BRANCH="${3:-main}"
# Get current user
CURRENT_USER=$(gh api user -q '.login')
if [ -z "$CURRENT_USER" ]; then
echo "ERROR: Could not determine current GitHub user"
exit 1
fi
# Validate Task exists and is open
TASK_DATA=$(gh issue view "$TASK_NUMBER" --json title,body,labels,state,assignees,url)
TASK_STATE=$(echo "$TASK_DATA" | jq -r '.state')
TASK_LABELS=$(echo "$TASK_DATA" | jq -r '.labels[].name')
if [ "$TASK_STATE" != "OPEN" ]; then
echo "ERROR: Task #$TASK_NUMBER is not open (state: $TASK_STATE)"
exit 1
fi
if ! echo "$TASK_LABELS" | grep -qx "Task"; then
echo "WARNING: Issue #$TASK_NUMBER does not have 'Task' label"
fi
# Check assignment
ASSIGNEES=$(echo "$TASK_DATA" | jq -r '.assignees[].login')
if [ -n "$ASSIGNEES" ] && ! echo "$ASSIGNEES" | grep -qx "$CURRENT_USER"; then
EXISTING=$(echo "$ASSIGNEES" | head -1)
echo "ERROR: Task #$TASK_NUMBER is already claimed by @$EXISTING"
exit 1
fi
# Claim the Task
if [ -z "$ASSIGNEES" ]; then
gh issue edit "$TASK_NUMBER" --add-assignee @me
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
gh issue comment "$TASK_NUMBER" --body "🏷️ Claimed by @$CURRENT_USER at $TIMESTAMP"
fi
echo "✓ Task #$TASK_NUMBER claimed by @$CURRENT_USER"
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.
- 2d ago First seen · 655 lines · 0 tokens per session scan C 58b10a8dd31f
task-executor-agent is an agent published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,417 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.