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.
/plugin marketplace add cboone/agent-harness-pluginsnpx agentmods add plugins/cboone/agent-harness-plugins/add-cobra-versiongit clone --depth 1 https://github.com/cboone/agent-harness-pluginsGrade A, and why
add-cobra-version 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.
What it actually says
{
"author": {
"name": "Christopher Boone"
},
"description": "Add a version subcommand with build metadata (version, commit hash, build date, Go runtime version, optional JSON output) to an existing Cobra-based Go CLI, wiring up ldflags in main.go, the cmd package, GoReleaser, and the Makefile.",
"homepage": "https://github.com/cboone/agent-harness-plugins",
"keywords": ["cli", "cobra", "go", "golang", "version"],
"license": "MIT",
"name": "add-cobra-version",
"repository": "https://github.com/cboone/agent-harness-plugins",
"skills": "./skills",
"version": "1.0.1"
}
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 · 14 lines scan A 570d31a80f48
add-cobra-version is a plugin published in the GitHub repository cboone/agent-harness-plugins (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
google-go-style
Skill that codifies the Google Go Style Guide into actionable rules for writing, reviewing, and refactoring Go code.
cli-printing-press
Generate production Go CLIs from API descriptions or OpenAPI specs.
cobra-viper
Definitive guide to building CLI applications with Cobra and Viper — command-first architecture, configuration management, environment variable binding, and in-memory CLI testing. Written by spf13, the original creator of both libraries.
go-spec-reviewer
Review Go design documents before implementation begins — catches over-engineering, missing error paths, interface misuse, and Cobra/Viper convention violations while a plan is still cheap to change.
go-ultimate
Opinionated Go development skill — architecture, conventions, production readiness, repo/CI hygiene, review, and MCP/agent patterns.
golang-skills
20 modular skills for idiomatic Go — each under 225 lines, backed by 48 reference files, 8 automation scripts (all with --json, --limit, --force), and 4 asset templates. Covers error handling, naming, testing, concurrency, interfaces, generics, documentation, logging, performance, and more. Activates automatically…