tingly-box: Skill for Claude Code

.claude/skills/update-libs/SKILL.md

update-libs is a skill for Claude Code from tingly-dev/tingly-box. It costs 80 tokens per session (872 once invoked), scanned A, original, MPL-2.0.

A procedure for updating three Go software-development libraries used by a project: the OpenAI, Anthropic, and Google GenAI SDKs.

In plain words
What is it for?
It is for changing the SDK version settings, updating Git submodules, reviewing fork-specific changes, and running build, vet, and test checks.
Why use it?
It provides a controlled way to sync library versions, handle API changes, preserve intentional patches, and check that the project still builds.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is tingly-dev/tingly-box's own configuration. It tells Claude Code how to work on tingly-box itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tingly-box configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go vet ./internal/... ./cli/... ./ai/... ./imbot/....

Reuse

Borrowing it

Nothing to install: this file belongs to tingly-dev/tingly-box. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tingly-dev/tingly-box/main/.claude/skills/update-libs/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/tingly-dev/tingly-box

Made for: Claude Code.

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-libs

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tingly-dev/tingly-box/update-libs"><img src="https://agentmods.dev/badge/skills/tingly-dev/tingly-box/update-libs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 872 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00080 $0.00872
Opus 5.5 $0.00032 $0.00349
Sonnet 5.5 $0.00016 $0.00174
Haiku 4.5 $0.00008 $0.00087

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

Security

Grade A, and why

update-libs 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 1mo 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.

.claude/skills/update-libs/SKILL.md · 76 lines

How it starts

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

Update libs/ SDK submodules

Wiring

  • Submodules: libs/openai-go, libs/anthropic-sdk-go, libs/go-genai, wired into go.mod via replace.
  • Version source of truth: OPENAI_GO_VERSION / ANTHROPIC_SDK_GO_VERSION / GO_GENAI_VERSION at the top of Taskfile.yml (branch or tag names).
  • task submodule:update checks out those refs and rewrites branch = in .gitmodules to match — never hand-edit .gitmodules.

Procedure

  1. Declare the target versions: edit the three vars in Taskfile.yml, then run:

    task submodule:update
    
  2. Network fallback if git fetch over HTTPS fails (SSH usually works):

    for d in libs/openai-go libs/anthropic-sdk-go libs/go-genai; do
      git -C $d config url."[email protected]:".insteadOf "https://github.com/"
    done
    

    Set it per-submodule — submodule repos don't inherit superproject config.

  3. Review the fork patches. The tingly-dev-* branches carry a small set of deliberate patches over upstream. Verify each still exists and still makes sense; a patch may have been deleted on purpose:

    git -C libs/<sdk> fetch origin
    git -C libs/<sdk> log --oneline origin/<upstream-ref>..<tingly-dev-ref>
    git -C libs/<sdk> diff --stat origin/<upstream-ref>..<tingly-dev-ref>
    

    Fork patch commits are prefixed tingly-dev and explain their intent in the commit body — read it before deciding anything.

  4. Build-fix loop:

    go build ./...
    

    Typical SDK breakage: plain fields become param.Opt[T] (packages/param). Write with param.NewOpt(x), read with x.Value (Opt[T] is a value struct; absent → zero value, no nil deref). Note that identically-named fields on different structs may differ — one may stay plain while another became Opt — so check the struct, not the field name.

  5. Verify:

    go vet ./internal/... ./cli/... ./ai/... ./imbot/...
    go test ./internal/protocol/...
    

    For any failure, first attribute it: SDK-related or environment? (Failing on network fetches, temp-HOME layout, etc. is unrelated to the bump.) Do not claim verification passed on failures you didn't triage.

Read the full file on GitHub · 76 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.

  1. 1mo ago First seen · 76 lines · 80 tokens per session scan A 617f765f47d6

Subscribe to this mod's changes

update-libs is a skill published in the GitHub repository tingly-dev/tingly-box (367 stars, last pushed today), licensed MPL-2.0. It adds 80 tokens to every session and 872 once invoked, 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-09-03.

Related

Other skills, from other repositories

golang-patterns

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications. Use when writing or reviewing Go code and idiomatic structure or conventions are in question.

gongyijie85/dsh-ecc · 44 tokens

golang-testing

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices. Use when writing Go tests — table-driven cases, subtests, benchmarks, fuzzing, or coverage.

gongyijie85/dsh-ecc · 56 tokens

golang-testing

Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.

affaan-m/ECC · 37 tokens

golang-patterns

Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.

affaan-m/ECC · 45 tokens

stack-trace-go-probe

Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.

opensquilla/opensquilla · 42 tokens

ax-go-gen

Use when writing Go code with github.com/ax-llm/ax/packages/go for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.

ax-llm/ax · 54 tokens