vigilante-issue-implementation-on-go

vigilante-issue-implementation-on-go is a skill for Codex from aliengiraffe/vigilante. It costs 36 tokens per session (899 once invoked), scanned A, original, Apache-2.0.

A coding workflow for completing a GitHub issue in a Go repository. Go is a programming language, and the workflow uses its standard formatting, testing, vetting, and security-checking tools.

In plain words
What is it for?
Use it when Vigilante assigns a Go issue: inspect the repository, implement the change, run relevant tests and checks, follow repository guidance, and report the result.
Why use it?
It provides a consistent way to make focused changes while checking style, behavior, common mistakes, and possible dependency vulnerabilities.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions AGENTS.md; mentions Codex.

Good fit Use it when Vigilante assigns a Go issue: inspect the repository, implement the change, run relevant tests and checks, follow repository guidance, and report the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go
Install

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.

Any agent
npx skills add aliengiraffe/vigilante --skill vigilante-issue-implementation-on-go
Clone the repo
git clone --depth 1 https://github.com/aliengiraffe/vigilante

Made for: Codex.

Wrote 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.

agentmods badge for vigilante-issue-implementation-on-go

README.md
[![agentmods](https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go/github.svg)](https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go)
Your own site
<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go/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.

agentmods 80×15 button for vigilante-issue-implementation-on-go

Your own site · 80×15
<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-go.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 899 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00899
Opus 5 $0.00018 $0.00449
Sonnet 5 $0.00007 $0.00180
Haiku 4.5 $0.00004 $0.00090

Measured 11d ago against content hash b034f114c085, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

vigilante-issue-implementation-on-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 11d 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.

skills/vigilante-issue-implementation-on-go/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vigilante Go Issue Implementation

Focus

  • Read the prompt for detected tech stacks, process hints, and Go security guidance before changing code.
  • Follow idiomatic Go conventions from Effective Go for naming, formatting, error handling, and package structure.
  • Keep changes scoped to the issue and do not broaden into unrelated style or lint fixes.

Go Tooling Workflow

  • Formatting: run gofmt or go fmt on all touched Go files. If the repository uses goimports, use that instead. Do not hand-format Go code.
  • Testing: run targeted go test ./path/to/package/... for changed packages first, then broader go test ./... when changes cross package boundaries. Use -race when practical.
  • Vetting: run go vet ./... on touched packages to catch common mistakes.
  • Vulnerability checking: run govulncheck ./... when it is installed and the change touches dependencies or security-sensitive code. If govulncheck is not available, note its absence and continue with other validation — do not fabricate output.
  • Linting: use the repository's established lint tooling. Prefer golangci-lint when configured (.golangci.yml or .golangci.yaml), or staticcheck when that is the project standard. If no project linter is configured, go vet is sufficient. Do not introduce a different linter unless the issue specifically requires it.
  • Dependencies: run go mod tidy after any dependency changes. Prefer standard library packages when they cover the need.

Effective Go Style

  • Use MixedCaps for multi-word names, not underscores.
  • Keep exported identifiers descriptive and unexported identifiers short.
  • Return errors rather than panicking.
  • Write doc comments on exported identifiers starting with the identifier name.
  • Keep packages focused and APIs minimal.

Security

  • Use crypto/rand for security-sensitive random values, not math/rand.
  • Prefer standard library crypto packages over third-party alternatives.
  • Use crypto/subtle.ConstantTimeCompare for comparing secret values.
  • Consider fuzz tests for parsers and input-handling logic (Go 1.18+ func FuzzXxx).
  • Do not store secrets, tokens, or credentials in source files.

Read the full file on GitHub · 48 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 11d ago First seen · 48 lines · 36 tokens per session scan A b034f114c085

Subscribe to this mod's changes

vigilante-issue-implementation-on-go is a skill published in the GitHub repository aliengiraffe/vigilante (40 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 899 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-30.