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 apideck-libraries/api-skills --skill apideck-gogit clone --depth 1 https://github.com/apideck-libraries/api-skillsWrote 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/apideck-libraries/api-skills/apideck-go)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/apideck-go"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/apideck-go.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.00118 | $0.01943 |
| Opus 5 | $0.00059 | $0.00971 |
| Sonnet 5 | $0.00024 | $0.00389 |
| Haiku 4.5 | $0.00012 | $0.00194 |
Grade A, and why
apideck-go 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 7d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apideck Go SDK Skill
Overview
The Apideck Unified API provides a single integration layer to connect with 200+ third-party services across accounting, CRM, HRIS, file storage, ATS, e-commerce, and more. The official Go SDK provides typed clients for all unified APIs.
Installation
go get github.com/apideck-libraries/sdk-go
IMPORTANT RULES
- ALWAYS use the
github.com/apideck-libraries/sdk-goSDK. DO NOT make rawnet/httpcalls to the Apideck API. - ALWAYS pass security, app ID, and consumer ID via functional options when creating the client.
- USE
ServiceIDon requests to specify which downstream connector to use. - ALWAYS check returned
errorvalues (idiomatic Go error handling). - USE
sdkgo.Pointer()helper for optional fields. - DO NOT store API keys in source code. Use environment variables.
Quick Start
package main
import (
"context"
"fmt"
"log"
"os"
sdkgo "github.com/apideck-libraries/sdk-go"
"github.com/apideck-libraries/sdk-go/models/components"
"github.com/apideck-libraries/sdk-go/models/operations"
)
func main() {
ctx := context.Background()
s := sdkgo.New(
sdkgo.WithConsumerID("your-consumer-id"),
sdkgo.WithAppID("your-app-id"),
sdkgo.WithSecurity(os.Getenv("APIDECK_API_KEY")),
)
res, err := s.Crm.Contacts.List(ctx, operations.CrmContactsAllRequest{
ServiceID: sdkgo.Pointer("salesforce"),
Limit: sdkgo.Pointer(int64(20)),
})
if err != nil {
log.Fatal(err)
}
for _, contact := range res.GetContactsResponse.Data {
fmt.Println(contact.Name)
}
}
SDK Patterns
Client Setup
import sdkgo "github.com/apideck-libraries/sdk-go"
s := sdkgo.New(
sdkgo.WithConsumerID("your-consumer-id"),
sdkgo.WithAppID("your-app-id"),
sdkgo.WithSecurity(os.Getenv("APIDECK_API_KEY")),
)
CRUD Operations
All resources follow the pattern: s.{Api}.{Resource}.{Operation}(ctx, request), returning (response, error).
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.
- 7d ago First seen · 256 lines · 118 tokens per session scan A 0800aafc3cc9
apideck-go is a skill published in the GitHub repository apideck-libraries/api-skills (3 stars, last pushed 8d ago), licensed Apache-2.0. It adds 118 tokens to every session and 1,943 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
go-style
Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…
go-docs
Go documentation conventions — a doc comment on every exported function, struct, type, and package, package comments in a dedicated doc.go for multi-file packages, godoc style (complete sentences beginning with the identifier's name), and LLM-ready CLI reference generation for cobra tools via a docgen helper built on…
go-project
Scaffold a Go project with the canonical layout — cmd/ entrypoints with a thin main, private packages under internal/ (no pkg/), a separate tools module pinning Go developer CLIs (invoked directly via go tool -modfile=tools/go.mod, no GOBIN), Node tools pinned in package.json and run from nodemodules/.bin, and a…
go-release
Release engineering for Go projects — GoReleaser v2 with version ldflags into an internal/version package, SBOMs and multi-arch container images, tag-triggered GitHub Actions releases, CI running build/vet/test -race/govulncheck with SHA-pinned actions, and Renovate coverage for gomod, tools, npm, and Actions. Use…
go-testing
Use when writing, reviewing, or running Go tests in test.go files — writing tests for a Go package, adding table-driven tests with t.Run subtests, testing a Go HTTP handler with httptest, adding a Go fuzz test or seed corpus, running or choosing go test flags (-race, -fuzz, -fuzztime), or deciding whether to use…
csharp-api-controller-standards
Defines the coding standards, patterns, and conventions for ASP.NET Core REST API controllers. Rules cover routing, HTTP verbs, response types, XML documentation, dependency injection, and asynchronous execution. Apply these rules uniformly to ensure a consistent, predictable, and well-documented API surface.