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/chainloop-dev/chainloop/upgrading-golangnpx skills add chainloop-dev/chainloop --skill upgrading-golanggit clone --depth 1 https://github.com/chainloop-dev/chainloopWhat 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.00048 | $0.00983 |
| Opus 5 | $0.00024 | $0.00491 |
| Sonnet 5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
upgrading-golang scanned grade A 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**IMPORTANT**: Before updating the version in common.mk, ALWAYS test that the Atlas version is available via the curl command: How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrading Golang Version
This skill automates the comprehensive Go version upgrade process across all components of the Chainloop project.
Process
1. Confirm Target Versions
Ask the user:
- What Go version they want to upgrade to (e.g., "1.25.3")
- Whether they also want to upgrade Atlas migrations Docker image (if yes, ask for target Atlas version, e.g., "0.38.0")
2. Get Docker Image Digest
Pull the official golang Docker image and extract its SHA256 digest:
docker pull golang:X.XX.X
Extract the SHA256 digest from the output (format: sha256:abc123...).
3. Update Source Code
Update the go directive in:
./go.mod
IMPORTANT: Do NOT update ./extras/dagger/go.mod per project policy.
Pattern to replace:
go X.XX.X
4. Update Docker Images
Update all Dockerfiles with the new version and SHA256 digest. See files-to-update.md for the complete list.
Pattern to replace:
FROM golang:X.XX.X@sha256:OLD_DIGEST AS builder
With:
FROM golang:X.XX.X@sha256:NEW_DIGEST AS builder
5. Update Documentation
Update the version reference in ./CLAUDE.md under "Key Technologies":
- **Language**: Go X.XX.X. To know how to upgrade go version, see docs/runbooks
6. Update Atlas Docker Image and CLI (Optional)
If the user requested an Atlas upgrade:
6a. Pull the Atlas Docker image and extract its SHA256 digest:
docker pull arigaio/atlas:X.XX.X
Extract the SHA256 digest from the output (format: sha256:abc123...).
6b. Update ./app/controlplane/Dockerfile.migrations:
Pattern to replace:
# from: arigaio/atlas:X.XX.X
# docker run arigaio/atlas@sha256:OLD_DIGEST version
# atlas version vX.XX.X
FROM arigaio/atlas@sha256:OLD_DIGEST as base
With:
# from: arigaio/atlas:X.XX.X
# docker run arigaio/atlas@sha256:NEW_DIGEST version
# atlas version vX.XX.X
FROM arigaio/atlas@sha256:NEW_DIGEST as base
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 136 lines · 48 tokens per session scan A e6c0ccec6a5e
upgrading-golang is a skill published in the GitHub repository chainloop-dev/chainloop (583 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 983 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
SafeAI Code Scanner
Security & Compliance Guardrail for AI-Generated Code (Vibe Coding). (v5.0.0).
ai-security
Use when building any feature that calls an LLM API, processes user input sent to a model, uses RAG or embeddings, deploys an AI agent with tool access, or makes AI-generated output visible to users or downstream systems.
compliance-and-audit
Use when a project requires a compliance framework mapping, when risks need formal documentation, when audit evidence must be collected, or when producing a compliance attestation before release. Applies to SOC 2, ISO 27001, GDPR, PCI DSS, NIST CSF, and DORA.
threat-modeling
Use when a new feature, architecture, or significant design decision is being made. Run before any code is written. Produces a structured STRIDE threat model and architecture review that feeds directly into security requirements and PR review.
security-and-hardening
Use when writing or reviewing code that handles user input, authentication, access control, cryptography, error handling, file uploads, or dependency management. Also activates when a pull request touches any security-sensitive component.