task-artifact-updates

A rule for keeping task records current while work is in progress. These records include plans, findings, verification results, and acceptance status.

In plain words
What is it for?
Use it when working in a task folder to record smoke-test results, non-obvious findings, plan status, and final acceptance criteria.
Why use it?
It keeps evidence and decisions with the task instead of leaving them only in chat. This makes completed checks and remaining issues easier to verify.

Cursor rule for Cursor

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 rules/rdudov/task-agent/task-artifact-updates
Clone the repo
git clone --depth 1 https://github.com/rdudov/task-agent

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 209 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.00000 $0.00209
Opus 5 $0.00000 $0.00105
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

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

Security

Grade A, and why

task-artifact-updates 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.

.cursor/rules/task-artifact-updates.mdc · 27 lines

What it actually says

Task artifact updates

When working in tasks/<id>/, follow skills/task-artifacts/SKILL.md.

Minimum before finishing:

  • verification.md covers each live smoke or task_contract.json required_live_evidence item
  • findings.md or findings-*.md records non-obvious findings
  • task.md has status done and checked acceptance criteria
  • reusable lookup knowledge has been promoted to an index, skill, or rule, or the task explains why it stays task-local

Immediately after a smoke check:

skills/task-artifacts/scripts/record_verification.sh tasks/TASK_DIR "gate_id" "short result without secrets"

Chat does not replace files in the task directory.

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 · 27 lines · 0 tokens per session scan A 517f90b13092

Subscribe to this mod's changes

task-artifact-updates is a cursor rule published in the GitHub repository rdudov/task-agent (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 209 tokens. 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.