Borrowing it
Nothing to install: this file belongs to mmadfox/swag2mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mmadfox/swag2mcp/main/.agents/skills/godeveloper/SKILL.mdgit clone --depth 1 https://github.com/mmadfox/swag2mcpWrote 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/mmadfox/swag2mcp/godeveloper)<a href="https://agentmods.dev/skills/mmadfox/swag2mcp/godeveloper"><img src="https://agentmods.dev/badge/skills/mmadfox/swag2mcp/godeveloper.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.00063 | $0.09208 |
| Opus 5 | $0.00032 | $0.04604 |
| Sonnet 5 | $0.00013 | $0.01842 |
| Haiku 4.5 | $0.00006 | $0.00921 |
Grade A, and why
godeveloper 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 5d 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 — 1,042 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Code Generation Skill — swag2mcp
This document defines how to write Go code for the swag2mcp project. It synthesizes the Uber Go Style Guide, Go Code Review Comments, Go Names, and Effective Go, adapted to this project's conventions.
1. Naming Conventions
1.1 General Rules
- MixedCase — never use underscores in names (
ServeHTTP, notServe_HTTP;maxLength, notmax_length). - Acronyms/Initialisms — keep consistent case:
ServeHTTP,IDProcessor,urlPony,appID. NeverServeHttp,UrlPony,AppId. Exception: generated protobuf code. - Distance rule — the further a name is from its declaration, the more descriptive it must be. Local variables with small scope get short names; exported package-level names get descriptive names.
1.2 Packages
- Short, lowercase, single-word names:
auth,cache,config,index,spec,types. - No underscores or mixed caps.
- Avoid meaningless names:
util,common,misc,api,types,interfaces. - Package name must match the last component of its import path.
- Package name should lend meaning to the names it exports.
auth.Basicnotauth.BasicAuth.
1.3 Files
- Lowercase with underscores for compound names:
oauth2_cc.go,api_key.go,parse_v3.go. - Test files:
*_test.gosuffix. - Generated files:
mock_*_test.goprefix (e.g.,mock_svc_test.go). doc.gofor package documentation.- When a file contains helpers or sub-types used exclusively by one other file, prefix the filename with the owner's name:
invoke_param_validator.go,invoke_response_writer.go,bootstrap_config_loader.go. This makes ownership obvious without needing package-level comments.
1.4 Types and Structs
- PascalCase for exported types:
LLMError,InvokeRequest,EndpointSearchItem. - camelCase for unexported types.
- Error types: PascalCase with
Errorsuffix:LLMError,ValidationError.
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.
- 5d ago First seen · 1,042 lines · 63 tokens per session scan A 4c90f9c12e16
godeveloper is a skill published in the GitHub repository mmadfox/swag2mcp (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 63 tokens to every session and 9,208 once invoked, about $0.0003 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
goai
GoAI is a Go SDK for AI applications. One unified API across 25+ LLM providers. Inspired by the Vercel AI SDK, adapted to Go idioms (generics, interfaces, channels).
wasm
WebAssembly (WASM) integration, WASI, component model, Rust/Go to WASM compilation. Use when implementing WASM modules, browser/edge compute, or polyglot runtime.
go-ops
Go development patterns, concurrency, error handling, testing, and project structure. Use for: golang, go, goroutine, channel, context, errgroup, go test, go mod, go build, interface, generics, table-driven tests, worker pool, sync.Mutex, sync.WaitGroup, pprof, go vet, golangci-lint, go workspace, functional options…
building-glamorous-tuis
Build terminal UIs with Charmbracelet (Bubble Tea, Lip Gloss, Gum). Use when: Go TUI, shell prompts/spinners, "make CLI prettier", adaptive layouts, async rendering, focus state machines, sparklines, heatmaps, kanban boards, SSH apps.
code-review-go
Deep Go-specific code review covering goroutine lifecycle, data races, error wrapping, domain modeling, and interface design. Applied in addition to the generic code-review skill when Go code is detected. Invoked when reviewing Go PRs, Go code changes, or performing Go-specific quality checks.
go-code-review
Use when reviewing Go code for performance, concurrency safety, security vulnerabilities, or readability issues.