speckit.agent-context.update

A command that refreshes the Spec Kit section inside one or more coding-agent instruction files, such as AGENTS.md or CLAUDE.md. Spec Kit is a toolkit for planning software from written specifications before coding.

In plain words
What is it for?
Use it after creating or changing a plan so coding agents point to the current plan file.
Why use it?
It keeps the managed instructions aligned with the newest project plan and avoids manually editing generated context sections.

Command

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/github/spec-kit/speckit.agent-context.update
Clone the repo
git clone --depth 1 https://github.com/github/spec-kit
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 392 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.00013 $0.00392
Opus 5 $0.00006 $0.00196
Sonnet 5 $0.00003 $0.00078
Haiku 4.5 $0.00001 $0.00039

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

Security

Grade A, and why

speckit.agent-context.update 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

extensions/agent-context/commands/speckit.agent-context.update.md · 28 lines

What it actually says

Update Coding Agent Context

Refresh the managed Spec Kit section inside the active coding agent's context/instruction file (e.g. CLAUDE.md, .github/copilot-instructions.md, AGENTS.md).

Behavior

The script reads the agent-context extension config at .specify/extensions/agent-context/agent-context-config.yml to discover:

  • context_file — the path of the coding agent context file to manage.
  • context_files — optional project-relative paths for multiple coding agent context files. When non-empty, the script updates each listed file and the list takes precedence over context_file.
  • context_markers.start / .end — the delimiters surrounding the managed section. Defaults to <!-- SPECKIT START --> and <!-- SPECKIT END --> when the field is missing.

It then creates, replaces, or appends the managed block so that the section points at the most recent plan path when one can be discovered (any plan.md under specs/, including nested scoped layouts such as specs/<scope>/<feature>/plan.md).

If context_files and context_file are empty, the command reports nothing to do and exits successfully. Context file paths must stay project-relative; absolute paths, Windows drive paths, backslash separators, and .. path segments are rejected.

Execution

  • Bash: .specify/extensions/agent-context/scripts/bash/update-agent-context.sh [plan_path]
  • PowerShell: .specify/extensions/agent-context/scripts/powershell/update-agent-context.ps1 [plan_path]

When plan_path is omitted, the script auto-detects the most recently modified specs/**/plan.md (searched recursively, so nested scoped layouts are discovered).

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 · 28 lines · 13 tokens per session scan A 215e3df01baf

Subscribe to this mod's changes

speckit.agent-context.update is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 392 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 commands, from other repositories