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/anhnguyen0905/codex-mcp/exec-gonpx skills add anhnguyen0905/codex-mcp --skill exec-gogit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/exec-go)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/exec-go"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/exec-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 | $0.00031 | $0.00296 |
| Opus 5 | $0.00015 | $0.00148 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
exec-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 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.
What it actually says
Go Idioms (embed when project is Go)
Go standards:
- Errors are values: check every err; wrap with context (`fmt.Errorf("doing x: %w", err)`);
no panic in library code — reserve it for truly unrecoverable programmer errors.
- Accept interfaces, return concrete types; keep interfaces small and defined where consumed.
- Concurrency: every goroutine has a clear owner and exit path (context cancellation, closed
channel, WaitGroup) — no fire-and-forget leaks; guard shared state with mutex or channels,
never both ad hoc; pass context.Context as the first parameter through call chains.
- Zero values matter: design structs whose zero value is usable, or provide a constructor.
- defer for cleanup immediately after acquiring the resource.
- Follow gofmt (non-negotiable), golangci-lint if configured, and standard layout the repo
already uses (cmd/, internal/, pkg/).
- Naming: short receiver names, MixedCaps not underscores, exported identifiers documented with
a leading-name comment.
- Tests: table-driven with subtests (t.Run), t.Helper() in helpers; use the repo's assertion
style (stdlib vs testify) — don't introduce a new one.
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 · 25 lines · 31 tokens per session scan A 4bd271633cec
exec-go is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 296 once invoked, about $0.0002 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
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
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-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…