update-tech-stack

A command that revises a project's technology-stack documentation when dependencies or technical choices change. A technology stack is the set of programming languages, libraries, services, and tools used by a project.

In plain words
What is it for?
Updating documentation after dependency upgrades, replacements, or other technical changes.
Why use it?
It keeps technical documentation aligned with changes in the codebase and its dependencies.

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/omed0/convex-selfhost-starterkit/update-tech-stack
Clone the repo
git clone --depth 1 https://github.com/Omed0/convex-selfhost-starterkit

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,034 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown 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.00011 $0.02034
Opus 5 $0.00005 $0.01017
Sonnet 5 $0.00002 $0.00407
Haiku 4.5 $0.00001 $0.00203

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

Security

Grade B, and why

update-tech-stack scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

<(grep -E '^\*\*.*:' .claude/docs/tech-stack.md | cut -d: -f1 | sed 's/\*//g' | sort)
.claude/commands/update-tech-stack.md · 326 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 326 lines · 11 tokens per session scan B bdbf3093a49d

Subscribe to this mod's changes

update-tech-stack is a command published in the GitHub repository Omed0/convex-selfhost-starterkit (2 stars, last pushed 10mo ago), with no licence file. It adds 11 tokens to every session and 2,034 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.