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 skills add orlando-japan/claude-code-setting --skill task-executiongit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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.
[](https://agentmods.dev/skills/orlando-japan/claude-code-setting/task-execution)<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/task-execution"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/task-execution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/task-execution"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/task-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.00788 |
| Opus 5.5 | $0.00013 | $0.00315 |
| Sonnet 5.5 | $0.00006 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task execution
You have a task list. Your job is to execute it faithfully — not to expand it, not to improve it, not to second-guess the spec while implementing.
Protocol
- Read the next task fully before writing code. Understand the verification before the implementation.
- Verify understanding — if anything in the task is ambiguous, stop and ask before coding. Asking after implementation wastes work.
- Implement just that task. Not the next one, not related cleanup, not "while I'm here" improvements.
- Run the task's verification. It must pass for this task to be done.
- Mark the task done in
tasks.md— edit the file, don't just say it in chat. - Commit. One task group per commit, referencing the task IDs or spec slug.
- Next task.
Golden rules
Don't expand scope
If task 3 says "add a redirect for logged-out users hitting /settings," the task is that redirect. Not redirects for all protected routes. Not a refactor of the middleware. Not better error messages. Just the redirect.
Don't re-plan
The spec was approved. Re-litigating design decisions during implementation wastes time and destabilizes the work. If you spot a real problem with the design, stop and surface it — don't silently change course.
Don't silently fix the spec
If a task reveals the spec is wrong — a requirement that can't be met, a scenario that's self-contradictory, a design that breaks an existing feature — stop. Report the discrepancy. Let the user decide whether to update the spec or adjust the implementation. Don't patch it invisibly.
Don't batch verification
Run each task's verification immediately after implementing it. If you batch and verify at the end, you can't tell which change broke what.
Don't skip tasks
Tasks are ordered for a reason. Skipping ahead risks building on foundations that aren't in place yet. If a task is genuinely impossible to do now, surface it.
When to stop
- A task's verification fails and you can't diagnose it in ~30 min → stop, ask the user or the original spec author.
- A task reveals a spec contradiction → stop, surface, wait for decision.
- The task takes longer than estimated by >2x → stop, re-estimate, let the user decide whether to continue.
- You're about to touch a file the spec didn't anticipate → stop, ask.
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.
- 1mo ago First seen · 66 lines · 32 tokens per session scan A b80e9a1d1559
task-execution is a skill published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 788 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
create-task
Create and verify recurring or one-shot reminders, scripts, agent jobs, reports, and interactive skill launches.
ima-skill
A unified IMA skill for managing personal notes and knowledge bases through the platform's APIs.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…
qqexmail
An email skill for Tencent Enterprise Email, a business email service, using the standard IMAP and SMTP protocols to read and send messages.
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and workflowbuildercreatetasks silence rules. Load whenever any of these tags appear or after calling workflowbuildercreatetasks.
suggest-automations
Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more. The system preloads it on onboarding threads, where the opening card already asked the user about themselves. Use it on…