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 verificationgit 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/verification)<a href="https://agentmods.dev/skills/insajin/autopus-adk/verification"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/verification/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.
<a href="https://agentmods.dev/skills/insajin/autopus-adk/verification"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.00525 |
| Opus 5 | $0.00008 | $0.00262 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
verification 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 6d 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.
What it actually says
Verification Skill
구현 완료 후 품질 게이트를 통과하고 수락 기준을 검증하는 스킬입니다.
검증 단계
1단계: 기능 검증
요구사항과 구현 결과를 대조합니다:
각 요구사항 항목에 대해:
- [ ] 구현됨
- [ ] 테스트로 검증됨
- [ ] 엣지 케이스 처리됨
2단계: 자동화 품질 게이트
# Go 전체 품질 게이트
set -e
# 1. 컴파일 확인
go build ./...
# 2. 테스트 + 레이스 컨디션
go test -race ./...
# 3. 커버리지 확인 (85% 이상)
go test -coverprofile=coverage.out ./...
go tool cover -func=coverage.out | tail -1
# 4. 린터
golangci-lint run
# 5. 벳
go vet ./...
3단계: LSP 품질 게이트
- 타입 에러: 0
- 린트 에러: 0
- 컴파일 에러: 0
4단계: 수락 기준 확인
EARS 요구사항 각각에 대해:
WHEN [조건] → [동작] 검증:
1. 조건 설정
2. 동작 실행
3. 결과 확인
5단계: 회귀 검증
기존 기능이 깨지지 않았는지 확인:
# 전체 테스트 스위트
go test ./...
# 이전 커밋과 비교
git stash
go test ./...
git stash pop
go test ./...
검증 보고서
## 검증 완료 보고서
### 기능 검증
- [x] 요구사항 1: [설명]
- [x] 요구사항 2: [설명]
### 품질 게이트
- Tests: ✅ N/N 통과 (커버리지: N%)
- Race: ✅ 레이스 컨디션 없음
- Lint: ✅ 경고 없음
- LSP: ✅ 에러 없음
### 회귀 검증
- 기존 테스트: ✅ 모두 통과
### 완료 상태
✅ 구현 완료, 배포 준비됨
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.
- 6d ago First seen · 95 lines · 16 tokens per session scan A 2a9e926a509f
verification is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 525 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
ui-testing
Create automated UI tests using Playwright for Streamlit and web applications. Use when writing end-to-end tests, automating UI testing, or testing new features.
playwright
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions…
component-testing
React component testing with Vitest, Testing Library, MSW, and renderHook. Use for Vitest setup, jsdom/happy-dom config, Testing Library queries, userEvent, component unit tests, testing React hooks, MSW API mocking, snapshot testing, or testing loading/error states. Complements playwright (E2E) and tdd-workflow…
backend-development
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
performance-testing
Performance testing, load testing, and benchmarking for APIs, databases, and web applications. Use when planning load tests, setting performance budgets, profiling bottlenecks, or validating scalability. Covers Locust, k6, pytest-benchmark, browser performance, and database query profiling.
test-strategy
Test planning and strategy for projects of any size. Use when defining what to test, choosing test types, setting coverage goals, building test pyramids, or planning quality gates. Produces TEST-STRATEGY.md with prioritized test plan. Routes to Tester agent for execution.