A command that checks how Tink was installed and compares local files with newer versions before showing an update command.

Use it to inspect an installation, identify files at risk during an update, and find the appropriate safe update command.

It helps avoid overwriting files that a user has changed and prevents applying consumer-install instructions to Tink's own source repository.

update — Command by dotoricode

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/dotoricode/tink-harness/update

Clone the repo

git clone --depth 1 https://github.com/dotoricode/tink-harness

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,214 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.

Model	Per session	Once invoked
Fable 5	$0.00017	$0.01214
Opus 5	$0.00009	$0.00607
Sonnet 5	$0.00003	$0.00243
Haiku 4.5	$0.00002	$0.00121

Measured yesterday against content hash 40b938b00e5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

.claude/commands/tink/update.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/tink:update

Tink를 최신 버전으로 안전하게 업데이트하는 방법을 안내합니다.

What this command does

This command does not run the update itself. It detects how Tink was installed in this project, diagnoses whether any user-modified files are at risk, and shows the correct command to run.

Procedure

Source-repo guard (first): If the project root contains all of templates/tink/, bin/install.js, and a package.json whose name is "tink-harness", this is the tink-harness source repository itself — not a consumer install. Skip the rest of the procedure and emit the "source repo" output (see below). Do not show plugin or npx update commands in this case.
Detect install source:
- If the project root (or cwd) has .claude-plugin/plugin.json and a top-level commands/ directory, Tink was installed via Claude Code plugin marketplace.
- Otherwise, treat it as an npx tink-harness install (standalone) installation.
Scan for files that have diverged from the latest installed templates (read-only inspection only):
- Always updated: .claude/commands/tink/, .claude/skills/tink/, .tink/tools/ — template changes always propagate here.
- Never overwritten once they exist: .tink/maintenance/ record files (ledger.jsonl, friction.jsonl, weave-queue.json) hold user history; the template only seeds them when missing.
- Preserved if user-modified: .tink/harnesses/, .tink/hooks/, .tink/memory/, .tink/config.json — respects weave customizations and local configuration.
Show the appropriate update path and a short list of files in the "preserved" category that have diverged.

Update path: Claude Code plugin

/plugin marketplace update tink-harness
/plugin update tink@tink-harness
/reload-plugins

If update is not detected, uninstall and reinstall:

/plugin uninstall tink@tink-harness
/plugin install tink@tink-harness

The plugin path is handled by Claude Code and does not touch the local .tink/ directory.

Read the full file on GitHub · 90 lines

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.

yesterday First seen · 90 lines · 17 tokens per session scan A 40b938b00e5f

Subscribe to this mod's changes

update is a command published in the GitHub repository dotoricode/tink-harness (1 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,214 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-31.

Debugging agent-harness agent-workflows agentic-coding ai-coding claude-code developer-tools

update

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/tink:update

What this command does

Procedure

Update path: Claude Code plugin

What this file has done since we first saw it

Other commands, from other repositories

diagnose

audit-agents-skills

boldguy-linkedin-answer

security-audit

audit-quiz-coverage

sync