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/jastice/rules_agents/go_helpernpx skills add jastice/rules_agents --skill go_helpergit clone --depth 1 https://github.com/jastice/rules_agentsWrote 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/jastice/rules_agents/go_helper)<a href="https://agentmods.dev/skills/jastice/rules_agents/go_helper"><img src="https://agentmods.dev/badge/skills/jastice/rules_agents/go_helper.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.00007 | $0.00023 |
| Opus 5 | $0.00003 | $0.00012 |
| Sonnet 5 | $0.00001 | $0.00005 |
| Haiku 4.5 | $0.00001 | $0.00002 |
Grade A, and why
Go Helper 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 6d 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 Helper
Skill for Go development workflows.
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.
- 6d ago First seen · 9 lines · 7 tokens per session scan A 6dd9d57a4614
Go Helper is a skill published in the GitHub repository jastice/rules_agents (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 23 once invoked, about $0.0000 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
vigilante-issue-implementation-on-go
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Go repository with idiomatic tooling and security guidance.
learning-plan
Use when 用户要求创建、调整或恢复 Python、Go、混合路线或面向目标代码的学习计划时。.
concept-teaching
Use when 用户希望学习或澄清一个 Python、Go 或当前目标代码所依赖的编程概念，并需要讲解与练习时。.
exercise-coach
Use when 学习者正在完成 Python、Go 或代码阅读练习，展示了尝试、遇到卡点，或明确要求获得提示时。.
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
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…