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 cboone/agent-harness-plugins --skill scaffold-go-cligit clone --depth 1 https://github.com/cboone/agent-harness-pluginsWrote 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/cboone/agent-harness-plugins/scaffold-go-cli)<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/scaffold-go-cli"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-go-cli/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.
<a href="https://agentmods.dev/skills/cboone/agent-harness-plugins/scaffold-go-cli"><img src="https://agentmods.dev/badge/skills/cboone/agent-harness-plugins/scaffold-go-cli.svg" alt="Reviewed on agentmods" width="80" 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.00136 | $0.03031 |
| Opus 5 | $0.00068 | $0.01515 |
| Sonnet 5 | $0.00027 | $0.00606 |
| Haiku 4.5 | $0.00014 | $0.00303 |
Grade A, and why
scaffold-go-cli 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 today.
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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Go CLI
Generate the full boilerplate for a new Go CLI project.
Workflow
1. Gather Project Information
If the user provided a project name in their request, use it as the project name and skip asking for it. Still ask for the remaining parameters (description, Viper, Charmbracelet TUI) unless already provided in the user's initial request.
Ask the user for these parameters:
- Project name -- kebab-case, used as the binary name, module path, and directory name (e.g.,
my-tool) - Short description -- one sentence, used in README, GoReleaser Homebrew cask, and the Cobra root command
Shortfield - Include Viper? -- whether to add Viper for config file management (adds
--configflag and~/.config/<name>/config.yamlsupport) - Include Charmbracelet TUI? -- whether to add bubbletea, lipgloss, and bubbles dependencies
If the user already provided some or all of these in their initial request, do not re-ask. Derive what you can from context.
2. Detect User Identity
Detect the user's GitHub username and full name for use in templates:
# GitHub username (for module paths, URLs, Homebrew tap)
gh api user -q .login
# Full name (for LICENSE copyright)
git config user.name
If either command fails or produces no output, ask the user to provide the value. Use the GitHub username wherever templates reference GITHUB-USERNAME and the full name wherever they reference COPYRIGHT-HOLDER.
3. Verify the Target Directory
The project should be scaffolded in a directory named after the project. If the current directory is already named after the project and is empty (or nearly empty), use it. Otherwise, create a subdirectory.
If the directory already contains Go files, warn the user before proceeding.
4. Initialize Git
Skip if already inside a git repository.
git init
5. Generate main.go
Read ./references/main-go.md for the main.go template and create the file from it.
- Replace
PROJECT-NAMEwith the project name - Replace
GITHUB-USERNAMEwith the detected GitHub username
What ships with it
12 files 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.
- references/ci-workflow.md 1.6 KB
- references/gitignore.md 826 B
- references/go-mod.md 1017 B
- references/goreleaser.md 2.5 KB
- references/homebrew-tap-token.md 2.8 KB
- references/license.md 1.4 KB
- references/main-go.md 734 B
- references/makefile.md 1.8 KB
- references/readme.md 1.3 KB
- references/release-workflow.md 1.2 KB
- references/root-go-with-viper.md 1.7 KB
- references/root-go-without-viper.md 921 B
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.
- today Changed · +18 lines c471076f48d2
- 6d ago First seen · 292 lines · 136 tokens per session scan A c0f5c19f412a
scaffold-go-cli is a skill published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 3,031 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
go-ci-workflow
Use when creating or refactoring GitHub Actions CI workflows for Go repositories. Covers repository-shape detection, Make-driven delegation with formal fallbacks, Go setup, caching, tool pinning, permissions, reusable workflows, and quality gate design.
go-ci
Continuous integration for Go projects: GitHub Actions pipelines, caching, golangci-lint setup, test/coverage gates, vulnerability scanning, build matrices, and Makefile targets. Use when: "set up CI", "GitHub Actions for Go", "add lint to the pipeline", "CI is slow", "coverage gate", "build matrix", "write a…
go-deploy
Build and deploy Go applications — version detection, static binaries, CGO, workspaces, and Dockerfile patterns. Use when deploying a Go project, or when go.mod is detected.
scaffold-go
Scaffold a complete Go project with CI/CD, release pipeline, Makefile, sr.yaml, .envrc, and standard files. Uses go toolchain and make as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Go CLI, service, or module, or when the user…
go-ci-setup
Set up a Go CI/CD pipeline with formatting, vetting, static analysis, tests, vulnerability scanning, and container build. Use when: creating CI for Go, adding checks to workflow. Do not use: for local development setup, non-CI automation.