create-task

A skill for creating a task on a configured project board. It builds the task body from the problem, required work, acceptance criteria, and context.

In plain words
What is it for?
It is for filing implementation or bug tasks on a project board when the repository has board settings configured.
Why use it?
It removes the need to know the board’s required format or send its credentials from the client. It also checks the codebase for evidence before drafting the task.

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/mimfort/rag_for_git/create-task
Any agent
npx skills add mimfort/rag_for_git --skill create-task
Clone the repo
git clone --depth 1 https://github.com/mimfort/rag_for_git

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 488 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.00031 $0.00488
Opus 5 $0.00015 $0.00244
Sonnet 5 $0.00006 $0.00098
Haiku 4.5 $0.00003 $0.00049

Measured 2d ago against content hash 39849a7a52ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-task 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.

plugin/skills/create-task/SKILL.md · 35 lines

What it actually says

Create Task

Reply in Russian. The server assembles the canonical body (Проблема / Что сделать / Критерии приёмки / Контекст), so clients never implement board markup or send credentials.

  1. Config. Read task_board from .review.yml; otherwise call get_board_config(). Read only type, project, create_target, done_target, and options. No board is a board-less no-op: explain it in Russian and stop.
  2. Draft. Build problem, steps, criteria, and context. Ground problem with search_codebase(...) and actual path:line evidence. Use technical Russian: no emoji, decorative separators, or marketing tone.
  3. Discover. Call get_board_targets(board_type=<type>, project=<project>, provider_options=<task_board.options or {}>). Its response has targets and options: each option declares required_for and choices. Use create_target only when it is among create-purpose targets. If a required create option is absent, discover it or ask the user; never guess. Empty discovery may create without a target only when no required option is missing.
  4. Confirm. Show the title, selected target label, selected options, and complete body. Write only after explicit confirmation; never write to the board silently.
  5. Write. Call
    create_task(title=…, problem=…, steps=[…], criteria=[…], context=…,
                board_type=<type>, project=<project>, target=<create_target or null>,
                provider_options=<task_board.options or {}>)
    
    On status == "error", report the reason in Russian and stop.
  6. Re-index. Call sync_board(board=<project or null>, board_type=<type>, provider_options=<task_board.options or {}>). Report the task key, URL, warnings, and result.

All reads stay fail-open. The confirmed create_task call is the only write.

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. 2d ago First seen · 35 lines · 31 tokens per session scan A 39849a7a52ee

Subscribe to this mod's changes

create-task is a skill published in the GitHub repository mimfort/rag_for_git (21 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 488 once invoked, about $0.0002 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

demo-write-user-stories

Reference implementation that writes functional user stories from a feature description, optionally grounded in an approved CEP context package per CONSUMING-CONTEXT-PACKAGE.md, with per-story citations and the standard tag/reverse-index loop. A worked example for downstream teams building their own context-consuming…

linkpranay-ai/context-engineering-protocol · 64 tokens

coograph-new-ticket

Start work on a new ticket. Runs pre-flight checks, investigates the codebase, and flows into OpenSpec proposal. Use when the user pastes a ticket, issue, or task description.

paullukic/coograph · 44 tokens

babysit

Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…

kirodotdev/KiroCrew · 137 tokens

agile-product-owner

../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.

alirezarezvani/claude-skills · 0 tokens

teamharness-task-delegation

Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.

agentscope-ai/AgentTeams · 56 tokens

gsd-executor

Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.

allgpt-co/QuickVoice · 36 tokens