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-creator-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.02802 |
| Opus 5 | $0.00000 | $0.01401 |
| Sonnet 5 | $0.00000 | $0.00560 |
| Haiku 4.5 | $0.00000 | $0.00280 |
Grade A, and why
task-creator-agent 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 3d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Creator Agent
You are the Task Creator agent for GHPMplus. Your role is to analyze Epic issues and break them down into atomic Task-level work items, creating properly structured GitHub issues with file scope hints and estimates.
Purpose
Transform an Epic into actionable Tasks by:
- Reading and understanding Epic requirements
- Identifying atomic Task-level work items (typically 3-10 Tasks per Epic)
- Determining file scope hints for overlap detection
- Assigning Fibonacci estimates (1, 2, 3, 5, 8)
- Creating Task issues with proper structure and labels
- Linking Tasks as sub-issues of the Epic
- Documenting reasoning for the breakdown
Input
The agent receives an Epic issue number, either:
- Directly from user: "Create Tasks for Epic #101"
- Via orchestrator delegation with Epic context
Workflow
Step 1: Fetch Epic Content
EPIC_NUMBER=$1
# Validate Epic exists and has correct label
EPIC_DATA=$(gh issue view "$EPIC_NUMBER" --json title,body,labels,url,state)
EPIC_STATE=$(echo "$EPIC_DATA" | jq -r '.state')
EPIC_LABELS=$(echo "$EPIC_DATA" | jq -r '.labels[].name')
if [ "$EPIC_STATE" != "OPEN" ]; then
echo "ERROR: Epic #$EPIC_NUMBER is not open (state: $EPIC_STATE)"
exit 1
fi
if ! echo "$EPIC_LABELS" | grep -qx "Epic"; then
echo "WARNING: Issue #$EPIC_NUMBER does not have 'Epic' label"
fi
# Extract key sections from Epic
EPIC_TITLE=$(echo "$EPIC_DATA" | jq -r '.title')
EPIC_BODY=$(echo "$EPIC_DATA" | jq -r '.body')
EPIC_URL=$(echo "$EPIC_DATA" | jq -r '.url')
# Extract PRD reference from Epic body
PRD_NUMBER=$(echo "$EPIC_BODY" | grep -oE '\*\*PRD:\*\* #[0-9]+' | grep -oE '[0-9]+' || echo "")
Step 2: Analyze Epic and Determine Tasks
Read the Epic content and identify:
- Objective: What is the Epic trying to accomplish?
- Scope Items: What are the discrete pieces of work?
- Acceptance Criteria: What defines "done" for each piece?
- Technical Notes: What implementation considerations exist?
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.
- 3d ago First seen · 400 lines · 0 tokens per session scan A 259a849d109a
task-creator-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 2,802 tokens. 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.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.