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 commands/el-feo/ai-context/executegit 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.00020 | $0.04997 |
| Opus 5 | $0.00010 | $0.02499 |
| Sonnet 5 | $0.00004 | $0.00999 |
| Haiku 4.5 | $0.00002 | $0.00500 |
Grade A, and why
execute 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 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.
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 — 620 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- TDD workflow (
/ghpm:tdd-task): Forfeat,fix,refactorcommit types - Non-TDD workflow: For
test,docs,chore,style,perfcommit types
Both workflows produce identical outputs: conventional commits, Task Report, and a PR that closes the Task.
Resolution order if omitted:
- If branch name matches
ghpm/task-<N>-*ortask-<N>-*, use N - Most recent open issue labeled
Taskassigned to @me:gh issue list -l Task -a @me -s open --limit 1 --json number -q '.[0].number' - Most recent open Task:
gh issue list -l Task -s open --limit 1 --json number -q '.[0].number'
<usage_examples> Execute a single task (auto-routes based on commit type):
/ghpm:execute task=#42
Execute all tasks under an epic:
/ghpm:execute epic=#10
Auto-resolve from branch or GitHub:
/ghpm:execute
</usage_examples>
<operating_rules>
- Always create a feature branch before making changes. Never commit directly to main/master.
- No local markdown artifacts. Do not write local status files; only code changes + GitHub issue/PR updates.
- Do NOT use the TodoWrite tool to track tasks during this session.
- Do not silently expand scope. If needed, create a new follow-up Task issue and link it.
- All commits and PR titles MUST follow Conventional Commits format for changelog generation.
- When routing to TDD, delegate fully to
/ghpm:tdd-task- do not duplicate its workflow. - When handling an Epic, process tasks sequentially (one PR per task, not batched).
- Exception: If multiple tasks modify the same file(s), batch them into a single PR with separate commits per task. Each commit must reference its task number.
- Minimize noise: comment at meaningful milestones. </operating_rules>
<routing_logic>
Determining Workflow Type
Read the Task issue body and extract the Commit Type field:
- Commit Type: `<type>`
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 · 620 lines · 20 tokens per session scan A e8b76356efc4
execute is a command published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 4,997 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.