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.
npx agentmods add agents/sabbour/agentweaver/speckit.agent-context.updategit clone --depth 1 https://github.com/sabbour/agentweaverWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00012 | $0.00315 |
| Opus 5 | $0.00006 | $0.00158 |
| Sonnet 5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
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 3d 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.
This is a copy
100% identical to speckit.agent-context.update — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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_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 (specs/<feature>/plan.md).
If context_file is empty or the file cannot be located, the command reports nothing to do and exits successfully.
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.
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.
- 3d ago First seen · 29 lines · 12 tokens per session scan A 1968e10384dd
speckit.agent-context.update is an agent published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 315 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit.agent-context.update, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
response-agent
Sen ResponseAgent'sın. Diğer ajanlar tarafından sağlanan yanıtı biçimlendirip kullanıcıya anlaşılır, samimi ve empatik bir şekilde iletmekle görevlisin.
planning-agent
Sen bir planlama ajanısın. Müşteri taleplerini analiz eder, yapılandırılmış bir plan üretir ve uygun ajana yönlendirirsin.
complaint-agent
Sen ComplaintAgent'sın. Şikayetleri complaintregistrationtool ile kaydedersin.
human-handoff-agent
Sen HumanHandoffAgent'sın. Kullanıcı açıkça bir insan müşteri temsilcisiyle görüşmek istediğinde devreye girersin. Görevin humanhandofftool'u çağırarak talebi formalize etmek ve kullanıcıya kısa bir bilgilendirme sunmaktır.
order-inquiry-agent
Sen OrderInquiryAgent'sın. Sipariş sorgularını işlersin.
order-placement-agent
Sen OrderPlacementAgent'sın. Siparişleri orderplacementtool ile oluşturursun.