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 majiang213/OpenClaw-MAS --skill cmd_go_testgit clone --depth 1 https://github.com/majiang213/OpenClaw-MASWrote 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/majiang213/openclaw-mas/cmd_go_test)<a href="https://agentmods.dev/skills/majiang213/openclaw-mas/cmd_go_test"><img src="https://agentmods.dev/badge/skills/majiang213/openclaw-mas/cmd_go_test.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.00033 | $0.00249 |
| Opus 5 | $0.00016 | $0.00125 |
| Sonnet 5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
cmd_go_test 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 4d 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
Delegate to the go-build-resolver agent.
Include in the task payload:
- Project path (the absolute path the user provided as the first argument)
- What to implement (function, class, module)
- Language version and test framework in use
- Any existing test fixtures or helpers to reuse
- Coverage target (default: 80%)
First, reply to the user briefly to confirm you are delegating to go-build-resolver.
Then call sessions_spawn:
{
"agentId": "go-build-resolver",
"sessionKey": "go-build-resolver",
"task": "<user's full request and all relevant context — the agent cannot see this conversation>",
"runTimeoutSeconds": 0
}
After sessions_spawn returns, relay the result to the user. Do not output anything after the spawn call until the result arrives.
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.
- 4d ago First seen · 33 lines · 33 tokens per session scan A e5033a95664e
cmd_go_test is a skill published in the GitHub repository majiang213/OpenClaw-MAS (5 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 249 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-09-03.
Other skills, from other repositories
tdd-workflow
Enforce practical Test-Driven Development for code changes in Go services. Use for new features, bug fixes, refactors, API changes, and new modules. Requires Red-Green-Refactor evidence, defect-hypothesis-driven tests, killer cases, and coverage gates (line + risk-path).
softdev-loop
Go software-development loop — implement, test, vet; repeat until green.
go-test
Skill "go-test" from rootwarp/claude-code-plugins-monorepo, covering /go-test and instructions.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications. Use when writing or reviewing Go code and idiomatic structure or conventions are in question.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.