tsk-add

A procedure for turning an agreed coding task from the current conversation into a queued asynchronous task using tsk add. It first summarizes the change, decisions, files, and acceptance criteria.

In plain words
What is it for?
Use it after discussing a design, architecture decision, or code change when you want the work queued for later execution. It asks clarifying questions until the task details are settled.
Why use it?
It prevents incomplete or misunderstood work from being sent to an agent before the requirements are agreed. It also creates a short task name and uses an available task template.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/dtormoen/tsk-tsk/tsk-add
Any agent
npx skills add dtormoen/tsk-tsk --skill tsk-add
Clone the repo
git clone --depth 1 https://github.com/dtormoen/tsk-tsk

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 964 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00964
Opus 5 $0.00008 $0.00482
Sonnet 5 $0.00003 $0.00193
Haiku 4.5 $0.00002 $0.00096

Measured yesterday against content hash 43b505802cea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tsk-add 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 yesterday.

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.

skills/tsk-add/skills/tsk-add/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Queue Task from Conversation

You are helping the user queue a task based on the conversation you just had. The user has been discussing a design, architecture decision, or code change with you, and now wants to queue it as an asynchronous task.

Available Templates

These are the task templates available for use with tsk add -t <template>:

!`tsk template list`

To see the full content of a template, run tsk template show <template>. When a task is created, the {{PROMPT}} placeholder in the template is replaced with whatever you pipe in via heredoc or pass via the -p flag, and any YAML frontmatter is stripped. The result is what gets sent to the agent.

Your Job

  1. Summarize the agreed-upon work: Review the conversation above and identify:

    • What change or feature was discussed
    • Key design decisions that were made
    • Any specific files, components, or areas mentioned
    • Acceptance criteria or requirements that were established
    • Ask clarifying questions about requirements, architecture choices, or task details
    • Only proceed once agreement has been reached
  2. Create a task name: Come up with a short, branch-friendly name (e.g., add-auth, refactor-api, fix-validation)

  3. Pick the best template: Based on the nature of the task, choose the template from the list above that best matches the work to be done (e.g., feat for new features, fix for bug fixes, refactor for restructuring, doc for documentation).

  4. Write the task prompt: Create a clear, self-contained prompt that includes:

    • The goal of the change
    • Key design decisions from the conversation
    • Specific files or areas to focus on (if discussed)
    • Acceptance criteria
  5. Queue the task: Use tsk add to create the task:

    • If you have already written a plan markdown file, prefer using --prompt-file
    • If you do not already have a plan in a file, prefer piping in the input
tsk add -t <template> -n "<task-name>" <<'EOF'
<task description>
EOF

# Alternatively:

tsk add -t <template> --prompt-file <path_to_the_plan>

Read the full file on GitHub · 110 lines

Changes

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.

  1. yesterday First seen · 110 lines · 16 tokens per session scan A 43b505802cea

Subscribe to this mod's changes

tsk-add is a skill published in the GitHub repository dtormoen/tsk-tsk (170 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 964 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.

Related

Other skills, from other repositories

git-commit-helper

Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.

alirezarezvani/claude-code-tresor · 55 tokens

code-reviewer

Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.

alirezarezvani/claude-code-tresor · 54 tokens

test-generator

Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.

alirezarezvani/claude-code-tresor · 55 tokens

api-documenter

Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.

alirezarezvani/claude-code-tresor · 48 tokens

readme-updater

Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.

alirezarezvani/claude-code-tresor · 49 tokens

security-auditor

Continuous security vulnerability scanning for OWASP Top 10, common vulnerabilities, and insecure patterns. Use when reviewing code, before deployments, or on file changes. Scans for SQL injection, XSS, secrets exposure, auth issues. Triggers on file changes, security mentions, deployment prep.

alirezarezvani/claude-code-tresor · 63 tokens