update-specs

update-specs is a cursor rule for Cursor from jaansokk/cursor_tools. It costs 63 tokens per session, scanned A, original, MIT.

A project rule to review the written specifications after implementation and update them when the completed work changes what they should say.

In plain words
What is it for?
Use it after building a feature, fixing a bug, or making another change covered by the project specifications.
Why use it?
It prevents the documentation used for future tasks from becoming outdated.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it after building a feature, fixing a bug, or making another change covered by the project specifications.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/jaansokk/cursor_tools/update-specs
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.

Clone the repo
git clone --depth 1 https://github.com/jaansokk/cursor_tools

Made for: Cursor.

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 update-specs

README.md
[![agentmods](https://agentmods.dev/badge/rules/jaansokk/cursor_tools/update-specs/github.svg)](https://agentmods.dev/rules/jaansokk/cursor_tools/update-specs)
Your own site
<a href="https://agentmods.dev/rules/jaansokk/cursor_tools/update-specs"><img src="https://agentmods.dev/badge/rules/jaansokk/cursor_tools/update-specs/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 update-specs

Your own site · 80×15
<a href="https://agentmods.dev/rules/jaansokk/cursor_tools/update-specs"><img src="https://agentmods.dev/badge/rules/jaansokk/cursor_tools/update-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 This file is loaded in full into every session.
When invoked 63 The same file — it is already loaded in full.
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.00063 $0.00063
Opus 5.5 $0.00025 $0.00025
Sonnet 5.5 $0.00013 $0.00013
Haiku 4.5 $0.00006 $0.00006

Measured 2mo ago against content hash 3bd81b9d4ff3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-specs 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 2mo 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/update-specs.mdc · 5 lines

What it actually says

After implementation has finished, always review if the specs need to be updated, so they will not lag behind (specs will be used for any subsequent work). Use _specs/spec-index.md to decide which spec(s) apply to the current task and should be updated.

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. 2mo ago First seen · 5 lines · 63 tokens per session scan A 3bd81b9d4ff3

Subscribe to this mod's changes

update-specs is a cursor rule published in the GitHub repository jaansokk/cursor_tools (1 stars, last pushed 7mo ago), licensed MIT. It adds 63 tokens to every session, about $0.0003 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-08-31.

Related

update-specs compared with cursor rules from other repositories

update-specs next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-specsjaansokk/cursor_toolsCursor rule17mo agoMITA63Cursor
app-router-patternstugkanboz/awesome-cursorrulesCursor rule241mo agoMITA2,554Cursor
test-patternstugkanboz/awesome-cursorrulesCursor rule241mo agoMITA2,177Cursor
testing-fundamentalstugkanboz/awesome-cursorrulesCursor rule241mo agoMITA26Cursor
data-fetchingkensaurus/cursor-kenjiCursor rule91mo agoMITA0Cursor
componentskensaurus/cursor-kenjiCursor rule91mo agoMITA0Cursor
gitkensaurus/cursor-kenjiCursor rule91mo agoMITA5Cursor