task-enrich

A task-improvement workflow for adding missing scenarios, edge cases, estimates, and a definition of done to an existing software task. It also checks the task against current specifications and discovery notes.

In plain words
What is it for?
Use it to enrich a draft task, update its status and estimate, resolve unclear acceptance criteria, and run a quality review.
Why use it?
It makes task requirements more complete and testable, especially for invalid input, permissions, empty results, concurrent actions, and limits.

Command for Claude Code

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 commands/iolairus/borderlint/task-enrich
Clone the repo
git clone --depth 1 https://github.com/iolairus/borderlint

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 307 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.00015 $0.00307
Opus 5 $0.00008 $0.00153
Sonnet 5 $0.00003 $0.00061
Haiku 4.5 $0.00002 $0.00031

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

Security

Grade A, and why

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

.claude/commands/task-enrich.md · 26 lines

What it actually says

Enrich the task $ARGUMENTS (a Jira key like PROJ-123, or a path) in backlog/tasks/.

Steps

  1. Locate the task file. If the argument is ambiguous or missing, list tasks with status: draft and ask.

    All additions are written in English (the repo's only content language).

  2. Cross-check against openspec/specs/ and the source discovery doc: does it contradict current behavior? Does it overlap another task?

  3. Enrich the task:

    • Scenarios — add missing unhappy paths: invalid input, permissions, empty states, concurrency, limits. Every Then must be observable/testable.
    • Notes & edge cases — record decisions and discovered constraints.
    • Estimate — propose one with a line of justification (points or hours per project convention).
    • Ambiguities — if any acceptance criterion is untestable as written, ask the user with AskUserQuestion rather than guessing.
  4. Update frontmatter: status: enriched, estimate.

  5. Run the task-reviewer subagent on the result. If it returns REVISE, fix the findings and re-run once.

  6. Suggest next: /task-jira <id> to export, or /opsx-propose referencing the task to start implementation.

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 · 26 lines · 15 tokens per session scan A b8968d51fb35

Subscribe to this mod's changes

task-enrich is a command published in the GitHub repository iolairus/borderlint (7 stars, last pushed 10d ago), licensed MIT. It adds 15 tokens to every session and 307 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-31.