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/xe/agent-plugins/xe-go-stylenpx skills add Xe/agent-plugins --skill xe-go-stylegit clone --depth 1 https://github.com/Xe/agent-pluginsWhat 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.00037 | $0.01981 |
| Opus 5 | $0.00018 | $0.00991 |
| Sonnet 5 | $0.00007 | $0.00396 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
xe-go-style 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 2d 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.
This is a copy
100% identical to xe-go-style — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xe's Go Style Guide
Write Go code following the conventions and patterns used by Xe Iaso.
Project Structure
├── cmd/ # Main applications (each subdirectory is a binary)
│ ├── x/ # CLI with subcommands
│ │ ├── main.go
│ │ └── cmd/ # Subcommand packages
│ └── sakurajima/ # Service binaries
│ ├── main.go
│ └── internal/ # Command-specific internal packages
├── internal/ # Private packages shared across commands
├── web/ # Web-related services and API clients
└── gen/ # Generated code (protobuf)
Package naming: lowercase, single words preferred (slog, flagenv, kahless).
CLI Pattern (CRITICAL)
All command-line tools MUST call flagenv.Parse() and then flag.Parse().
package main
import (
"flag"
"github.com/facebookgo/flagenv"
)
var (
bind = flag.String("bind", ":8080", "HTTP bind address")
dbLoc = flag.String("db-loc", "", "Database location")
)
func main() {
flagenv.Parse()
flag.Parse()
}
Configuration loading order: flags → env vars (flagenv) → flags (final override).
Subcommands
Use github.com/google/subcommands for subcommand-based CLIs:
package main
import (
"context"
"flag"
"os"
"github.com/facebookgo/flagenv"
"github.com/google/subcommands"
)
func main() {
flagenv.Parse()
subcommands.Register(subcommands.HelpCommand(), "")
subcommands.Register(subcommands.FlagsCommand(), "")
subcommands.Register(subcommands.CommandsCommand(), "")
subcommands.Register(&serveCmd{}, "")
subcommands.Register(&versionCmd{}, "")
os.Exit(int(subcommands.Execute(context.Background())))
}
type serveCmd struct {
dbLoc string
}
func (c *serveCmd) Name() string { return "serve" }
func (c *serveCmd) Synopsis() string { return "Start the server" }
func (c *serveCmd) Usage() string {
return "serve [flags]\nStart the HTTP server.\n"
}
func (c *serveCmd) SetFlags(f *flag.FlagSet) {
f.StringVar(&c.dbLoc, "db-loc", "", "Database location")
}
func (c *serveCmd) Execute(ctx context.Context, f *flag.FlagSet, args ...interface{}) subcommands.ExitStatus {
// Implementation
return subcommands.ExitSuccess
}
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.
- 2d ago First seen · 314 lines · 37 tokens per session scan A 8b8e81eacc42
xe-go-style is a skill published in the GitHub repository Xe/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,981 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to xe-go-style, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-data-structures
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing…
golang-dependency-management
Dependency management for Golang projects — go.mod and go.sum, go get install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, govulncheck scanning of the module tree, outdated dependency and binary size auditing, vendoring, tool directives, and go.work workspaces. Use…
golang-spf13-viper
Golang configuration library using spf13/viper — layered precedence (flag > env > file > KV > default), BindPFlag/BindPFlags, SetEnvPrefix + SetEnvKeyReplacer + AutomaticEnv, ReadInConfig + ConfigFileNotFoundError, Unmarshal + mapstructure struct tags, Sub for sub-trees, WatchConfig + OnConfigChange for hot reload…