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 skills/internet-development/ts-general-agent/task-executionnpx skills add internet-development/ts-general-agent --skill task-executiongit clone --depth 1 https://github.com/internet-development/ts-general-agentWhat 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.00016 | $0.00491 |
| Opus 5 | $0.00008 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
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 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Prompt
You are executing a task from a collaborative multi-SOUL plan.
Repository: {{repoFullName}} Plan: {{planTitle}} Goal: {{planGoal}}
Your Task: Task {{taskNumber}} - {{taskTitle}}
{{filesSection}}
{{dependenciesSection}}
Description: {{taskDescription}}
Constraints
- Stay focused on THIS task only - Do not work on other tasks
- Never commit directly to main - You are on a feature branch, commit there
- NEVER run
git merge,git rebase,git pull, orgit fetch— your feature branch must contain ONLY your task's commits, nothing else. Merging other branches contaminates the PR with unrelated commits. - NEVER switch branches — stay on the current feature branch for the entire task. Do not
git checkout mainor any other branch. - Commit your changes with message:
task({{taskNumber}}): {{taskTitle}} - Commit with descriptive messages referencing the task number in each commit
- If blocked, explain clearly what's preventing completion
- Test your changes if tests exist — but if the test runner is not installed (e.g.
vitest: command not found,jest: not found), that is NOT a task failure. Skip tests and continue. The verification system handles this separately. - Keep changes minimal - only what's needed for this task
- You MUST produce at least one git commit with file changes. The verification system requires git changes on the feature branch. If the task description seems to require only non-code actions (posting comments, updating issues), translate it into a file change — update documentation, a tracking file, or a relevant config. A task with zero git changes will fail.
Process
- Read and understand the task description
- Explore the codebase to understand context
- Verify you are on the correct feature branch (run
git branchto confirm — NOT main) - Make the necessary changes
- Test if possible
- Commit with the specified message format
- Report what was done
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 · 51 lines · 16 tokens per session scan A 520c74d3c8e9
Task Execution is a skill published in the GitHub repository internet-development/ts-general-agent (11 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 491 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 skills, from other repositories
maintain-model-list
Maintain the supported LLM model list: add a new model, or run routine maintenance to verify availability and discover new models worth adding. Use when the user asks to add/support a model, update the model list, or check model availability.
update-changelog
Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent.
git-cleanup
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
pre-impl-discussion
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.
gh-pr-description
Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.