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 codeready-toolchain/tarsy --skill golang-type-safetygit clone --depth 1 https://github.com/codeready-toolchain/tarsyWrote 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/codeready-toolchain/tarsy/golang-type-safety)<a href="https://agentmods.dev/skills/codeready-toolchain/tarsy/golang-type-safety"><img src="https://agentmods.dev/badge/skills/codeready-toolchain/tarsy/golang-type-safety/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/codeready-toolchain/tarsy/golang-type-safety"><img src="https://agentmods.dev/badge/skills/codeready-toolchain/tarsy/golang-type-safety.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00812 |
| Opus 5 | $0.00019 | $0.00406 |
| Sonnet 5 | $0.00008 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
golang-type-safety 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Type Safety
Use typed constants and named types instead of magic strings and numbers. This catches misuse at compile time and makes intent explicit.
Named String Types for Enums
When a value comes from a defined set (e.g. ent-generated enums, config enums), use the named type:
// Bad — magic string, no compile-time checking
publishStageStatus(ctx, pub, sid, stgID, name, idx, "investigation", status)
// Good — typed constant, typos caught at compile time
publishStageStatus(ctx, pub, sid, stgID, name, idx, stage.StageTypeInvestigation, status)
Function Signatures
Accept the named type, not string, when the parameter is always one of a known set:
// Bad — caller can pass any string
func publishStageStatus(ctx context.Context, ..., stageType string, status string)
// Good — compiler enforces valid stage types
func publishStageStatus(ctx context.Context, ..., stageType stage.StageType, status string)
Convert to string at serialization boundaries (JSON payloads, DB queries, log messages):
payload.StageType = string(stageType)
Warning: Direct Casting Does Not Validate
stage.StageType(s) compiles but does not check whether s is a known value.
Always use a parse helper at API/deserialize boundaries where the input is untrusted:
// Bad — silently accepts unknown values
stageType := stage.StageType(req.StageType)
// Good — rejects unknown values at the boundary
stageType, err := parseStageType(req.StageType)
if err != nil {
return nil, err
}
parseStageType Helper
Define this once near the package entry point (e.g., handler or service layer):
// parseStageType converts a raw string from an API payload or query parameter
// into a stage.StageType, returning an error for unknown values.
//
// Allowed values: stage.StageTypeInvestigation, stage.StageTypeSynthesis,
// stage.StageTypeChat, stage.StageTypeExecSummary, stage.StageTypeScoring.
func parseStageType(s string) (stage.StageType, error) {
switch stage.StageType(s) {
case stage.StageTypeInvestigation,
stage.StageTypeSynthesis,
stage.StageTypeChat,
stage.StageTypeExecSummary,
stage.StageTypeScoring:
return stage.StageType(s), nil
default:
return "", fmt.Errorf("unknown stage type %q", s)
}
}
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.
- 11d ago First seen · 116 lines · 38 tokens per session scan A 115bd6e1649d
golang-type-safety is a skill published in the GitHub repository codeready-toolchain/tarsy (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 812 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
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.
performant-go
Strategies for high-performance Go systems (Goroutines, Channels, Pprof, Memory Alignment).
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.