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 skills add Insajin/autopus-adk --skill migrationgit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/migration)<a href="https://agentmods.dev/skills/insajin/autopus-adk/migration"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/migration.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.1 | $0.00023 | $0.00997 |
| Opus 5 | $0.00012 | $0.00498 |
| Sonnet 5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
migration 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Skill
언어, 프레임워크, 라이브러리 버전 업그레이드를 안전하게 수행하는 스킬입니다.
마이그레이션 프로세스
1단계: 영향 분석
# Go 모듈 의존성 확인
go list -m -u all # 업데이트 가능한 모듈 목록
go mod graph # 의존성 그래프
# 브레이킹 체인지 확인
# 릴리스 노트, CHANGELOG, migration guide 확인
분석 항목:
- 제거된 API (removed/deprecated)
- 시그니처 변경 (parameter/return type)
- 동작 변경 (behavior change)
- 새 필수 설정 (required config)
2단계: 호환성 테스트
# 현재 테스트 전체 통과 확인 (기준선)
go test -race ./...
# 버전 업그레이드
go get -u github.com/[email protected]
go mod tidy
# 컴파일 에러 확인
go build ./...
# 테스트 재실행
go test -race ./...
3단계: 점진적 마이그레이션
소규모 변경 (1-2개 API 변경):
- 직접 수정 후 커밋
중규모 변경 (5-10개 파일):
- 호환 레이어 작성 → 사용처 변경 → 호환 레이어 제거
- 각 단계별 커밋
대규모 변경 (메이저 버전):
- Branch by Abstraction 패턴 적용
- 피처 플래그로 점진적 전환
4단계: 검증
go test -race ./...
go vet ./...
golangci-lint run
Go 버전 업그레이드
go.mod 업데이트
# Go 버전 변경
go mod edit -go=1.23
# 새 기능 활용 가능 여부 확인
go build ./...
go test ./...
주요 버전별 변경 사항 확인
- 새 표준 라이브러리 함수
- 삭제/변경된 동작
- 새 린트 규칙
의존성 업그레이드 전략
안전한 순서
1. 패치 버전 업그레이드 (1.2.3 → 1.2.4) — 버그 수정
2. 마이너 버전 업그레이드 (1.2.x → 1.3.0) — 하위 호환 기능 추가
3. 메이저 버전 업그레이드 (v1 → v2) — 브레이킹 체인지 가능
Dependabot / Renovate 활용
# .github/dependabot.yml
version: 2
updates:
- package-ecosystem: gomod
directory: /
schedule:
interval: weekly
reviewers:
- team/backend
브레이킹 체인지 대응 패턴
Adapter Pattern
// 구 API를 새 API로 래핑
type LegacyAdapter struct {
newClient *NewClient
}
func (a *LegacyAdapter) OldMethod(args OldArgs) OldResult {
newArgs := convertArgs(args)
newResult := a.newClient.NewMethod(newArgs)
return convertResult(newResult)
}
Feature Flag
func handler(w http.ResponseWriter, r *http.Request) {
if config.UseNewAPI {
newHandler(w, r)
} else {
oldHandler(w, r)
}
}
Parallel Run (Shadow Traffic)
func handler(w http.ResponseWriter, r *http.Request) {
oldResult := oldHandler(r)
// 백그라운드에서 새 구현 실행 (비교용)
go func() {
newResult := newHandler(r)
compareResults(oldResult, newResult)
}()
respond(w, oldResult) // 구 결과 반환
}
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.
- 3d ago First seen · 155 lines · 23 tokens per session scan A 06583649b437
migration is a skill published in the GitHub repository Insajin/autopus-adk (109 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 997 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-09-03.
Other skills, from other repositories
go
Use when writing, reviewing, testing, or shipping Go code and HTTP services: idioms, %w error wrapping, goroutine/context/errgroup concurrency, net/http 1.22 routing, log/slog, project layout, table-driven tests, Go hardening. NOT language-agnostic threat modeling (that is secure-coding), NOT Dockerfile/CI shipping…
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
swiftui-view-refactor
Refactor a SwiftUI view file for consistent property ordering, MV patterns, view model handling, and Observation usage; split an oversized body via same-file computed view properties or MARK-organized extensions. Use when asked to clean up a SwiftUI view's layout, reorder its properties, or standardize…
watchos-development
Use when building or reviewing a watchOS app or WatchKit extension — app structure and independent-app configuration, Watch Connectivity / companion-app sync, complications and Smart Stack widgets, controls or Live Activities on watch, background refresh and networking limits, watchOS-specific SwiftUI design…
swift-concurrency
Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3)…
react-dev
This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React…