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.
npx agentmods add skills/tingly-dev/tingly-box/update-libsnpx skills add tingly-dev/tingly-box --skill update-libsgit clone --depth 1 https://github.com/tingly-dev/tingly-boxWrote 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.
[](https://agentmods.dev/skills/tingly-dev/tingly-box/update-libs)<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="Measured on agentmods" height="20"></a>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.00080 | $0.00872 |
| Opus 5 | $0.00040 | $0.00436 |
| Sonnet 5 | $0.00016 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
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 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.
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 intogo.modviareplace. - Version source of truth:
OPENAI_GO_VERSION/ANTHROPIC_SDK_GO_VERSION/GO_GENAI_VERSIONat the top ofTaskfile.yml(branch or tag names). task submodule:updatechecks out those refs and rewritesbranch =in.gitmodulesto match — never hand-edit.gitmodules.
Procedure
-
Declare the target versions: edit the three vars in
Taskfile.yml, then run:task submodule:update -
Network fallback if
git fetchover 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/" doneSet it per-submodule — submodule repos don't inherit superproject config.
-
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-devand explain their intent in the commit body — read it before deciding anything. -
Build-fix loop:
go build ./...Typical SDK breakage: plain fields become
param.Opt[T](packages/param). Write withparam.NewOpt(x), read withx.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 becameOpt— so check the struct, not the field name. -
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.
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 · 76 lines · 80 tokens per session scan A 617f765f47d6
update-libs is a skill published in the GitHub repository tingly-dev/tingly-box (346 stars, last pushed yesterday), licensed MPL-2.0. It adds 80 tokens to every session and 872 once invoked, about $0.0004 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-09-03.
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.
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.
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.
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.
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.
golang-expert
Go programming expert for goroutines, channels, interfaces, modules, and concurrency patterns.