task-close

task-close is a skill for Claude Code from Mozurok/fhorja.dev. It costs 110 tokens per session (7,830 once invoked), scanned A, original, MIT.

A task-closing workflow that checks whether an engineering task is finished, marks its state as closed, and moves its folder to an archive.

In plain words
What is it for?
Use it to verify completion conditions, update TASKSTATE.md, and archive a finished task.
Why use it?
It prevents unfinished tasks from being closed and keeps active work separate from completed records.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; reads ~/.codex paths; mentions Codex.

Good fit Use it to verify completion conditions, update TASKSTATE.md, and archive a finished task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mozurok/fhorja.dev/task-close
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.

Any agent
npx skills add Mozurok/fhorja.dev --skill task-close
Clone the repo
git clone --depth 1 https://github.com/Mozurok/fhorja.dev

Made for: Claude Code.

Wrote 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.

agentmods badge for task-close

README.md
[![agentmods](https://agentmods.dev/badge/skills/mozurok/fhorja.dev/task-close/github.svg)](https://agentmods.dev/skills/mozurok/fhorja.dev/task-close)
Your own site
<a href="https://agentmods.dev/skills/mozurok/fhorja.dev/task-close"><img src="https://agentmods.dev/badge/skills/mozurok/fhorja.dev/task-close/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.

agentmods 80×15 button for task-close

Your own site · 80×15
<a href="https://agentmods.dev/skills/mozurok/fhorja.dev/task-close"><img src="https://agentmods.dev/badge/skills/mozurok/fhorja.dev/task-close.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,830 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00110 $0.07830
Opus 5.5 $0.00044 $0.03132
Sonnet 5.5 $0.00022 $0.01566
Haiku 4.5 $0.00011 $0.00783

Measured 15d ago against content hash 46c0f4aff0e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

task-close 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 15d 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.

.claude/skills/task-close/SKILL.md · 202 lines

How it starts

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

Output contract, in brief. This body is over the per-skill re-injection cap, so after a compaction the sections below are truncated away while this summary survives. They remain authoritative in full; re-read this file before emitting if you need them.

  • Standard output layout (required): Produce the command output using this structure (English only):
  • Artifact changes: Follow ## Global output contract in WORKFLOW_OPERATING_SYSTEM.md for APPLIED / PROPOSED / SKIP rules. Every listed file...
  • Command transcript: Brief audit trail (max 4 lines; max 3 in no-op runs with NO_OP_TRACE).
  • Handoff: Use the adaptive ending format of WORKFLOW_OPERATING_SYSTEM.md ## Global output contract. Every Handoff is one fenced text b...
  • Definition of done (command output): Done-conditions checklist is complete: each of the five conditions has a verdict (met / not-met / waived) with evidence or an expl...

Act as a senior/staff engineering workflow closure operator.

Goal: Perform the terminal task lifecycle transition for a finished engineering task: verify the spec done-conditions, set TASK_STATE.md to its final closed state, and move the task folder from active/ to archive/. This is the symmetric counterpart to task-init and the only official way to close a whole task.

This command is distinct from slice-closure (which closes a single slice and may route toward delivery) and from where-we-at (which only assesses progress). Use task-close exactly once per task, when the whole task is ending.

Mandatory context bootstrap (before any output):

  • Resolving the spec and wos/<topic>.md: canonical repository FIRST. Otherwise use active-adapter docs: ~/.claude/workflow-docs (CLAUDE_WORKFLOW_DOCS_DIR), ~/.cursor/workflow-docs (WORKFLOW_DOCS_DIR; project .cursor/workflow-docs on project installs), ~/.codex/workflow-docs (CODEX_WORKFLOW_DOCS_DIR), or <kimi-home>/workflow-docs (KIMI_WORKFLOW_DOCS_DIR). Nonempty overrides win. Kimi home: KIMI_CODE_HOME, else existing ~/.kimi-code, else existing ~/.kimi, default ~/.kimi-code. Use one root for both paths; try other adapters if absent or unknown. Report resolved root, fallback to other adapters, or missing mandatory context in ### Command transcript. Installed snapshots refresh and prune retired topics only on sync.
  • Read these sections in WORKFLOW_OPERATING_SYSTEM.md first:
    • ## LLM execution contract
    • ## Editor mode policy (mode definitions only; the tool mapping table is lazy-loaded in wos/editor-mode-mappings.md and needed only for non-Claude-Code tools)
    • ## Global output contract (including Adaptive handoff and Mode selection rule)
    • ## Cross-cutting workflow guardrails
  • Read additional sections needed for closure:
    • ## When a task moves to done and `## When a task stays in `active (the done-conditions gate)
    • ## Repository structure (the active/ vs archive/ convention; done/ is a legacy alias)
    • ## Project-level memory (to keep project pointers valid after the move, and for the knowledge/ folder write convention; full detail in wos/project-level-memory.md)
  • Read the active task's memory:
    • TASK_STATE.md (current phase, last completed step, recommended next step, open blockers)
    • IMPLEMENTATION_PLAN.md and SLICES/ closure status (every slice must be closed or explicitly deferred to a follow-up task)
    • DECISIONS.md (confirm no decision is still open)
    • SOURCE_OF_TRUTH.md ## Workspace section, if present (the worktree path and task branch to tear down per ADR-0074)
  • Read canonical command inventory when a clone is available; otherwise use installed Fhorja commands and skills.
  • Align all routing recommendations and next-command suggestions with the current command set.
  • Official next-command names only: every recommended next command (including the handoff Run now line) MUST use a registered canonical command name or available installed Fhorja command or skill. Never invent names. One exception: Run now: none with Mode: N/A declares the chain ended with no honest next step, defined under ### Official command names (routing integrity) (ADR-0126); use it only then, never to end a chain that has a real next step.

Read the full file on GitHub · 202 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. 15d ago Changed · -1 lines · -67 tokens per session 46c0f4aff0e9
  2. 18d ago Changed · +3 lines ad784b421ad9
  3. 25d ago Changed · -6 lines 6413dcedb51a
  4. 26d ago Changed · -18 lines 9c31b39d8021
  5. 1mo ago First seen · 224 lines · 177 tokens per session scan A ad491bd9d25e

Subscribe to this mod's changes

task-close is a skill published in the GitHub repository Mozurok/fhorja.dev (10 stars, last pushed 15d ago), licensed MIT. It adds 110 tokens to every session and 7,830 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

issue-creation

Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.

Gentleman-Programming/gentle-ai · 30 tokens

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens

ijfw-workflow

Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.

FerroxLabs/ijfw · 70 tokens

ijfw-plan

Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…

FerroxLabs/ijfw · 95 tokens

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

ijfw-complete-milestone

Use when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger: 'milestone complete', 'ship milestone', 'wrap milestone', 'complete milestone ', /ijfw-complete-milestone.

FerroxLabs/ijfw · 62 tokens