upgrade

A command for upgrading the trs tool, a program whose older versions point users to newer documentation.

In plain words
What is it for?
Use it to upgrade trs and find the latest documentation for that process.
Why use it?
It provides the direct upgrade path for older trs versions and sends users to the current upgrade instructions.

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/dpeluche/trs/upgrade
Clone the repo
git clone --depth 1 https://github.com/dPeluChe/trs
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 58 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.00058
Opus 5 $0.00000 $0.00029
Sonnet 5 $0.00000 $0.00012
Haiku 4.5 $0.00000 $0.00006

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

Security

Grade A, and why

upgrade 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.

docs/commands/upgrade.md · 7 lines

What it actually says

Moved

This doc is now at docs/features/upgrade.md.

Older trs binaries (≤ v0.5.9) link here from their "More:" hint. Upgrade with trs upgrade to pick up the direct link.

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

Subscribe to this mod's changes

upgrade is a command published in the GitHub repository dPeluChe/trs (10 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 58 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.