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 pilinux/gorest --skill build-rungit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/build-run)<a href="https://agentmods.dev/skills/pilinux/gorest/build-run"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/build-run/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/pilinux/gorest/build-run"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/build-run.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.00022 | $0.00367 |
| Opus 5 | $0.00011 | $0.00183 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
build-run 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 9d 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
Build and Run
When to Use
- Confirm the codebase compiles, reproduce a runtime issue locally, or validate environment-dependent changes.
Rules
- Do not use production credentials or external services unless the user provides safe mocks/stubs.
- Use
source setTestEnv.shfor local env needed by tests or the app. - Prefer reproducible, minimal commands and capture key output lines.
Commands
- Compile:
go build -v ./... - Format:
go fmt ./... - Vet:
go vet -v ./... - Tidy deps:
go mod tidy - Run tests that reproduce an issue:
source setTestEnv.sh && go test -run <TestName> ./pkg/path - Start example app:
cd example2/cmd/app && go run main.go(use with test env)
Output
- Result: success or failure.
- Key logs: first relevant error or stack lines.
- Minimal repro: 1-3 commands.
- Next steps: which logs/files to inspect or which mocks to add.
Examples
- "Does the project compile?" - run
go build -v ./...and report. - "Reproduce failing integration test X" - provide commands and first failing lines.
Related Skills
test-runner,ci-orchestrator,fix-suggester
References
AGENTS.md(build and run commands),setTestEnv.sh,llms.txt
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.
- 9d ago First seen · 50 lines · 22 tokens per session scan A d8e1337aa441
build-run is a skill published in the GitHub repository pilinux/gorest (504 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 367 once invoked, about $0.0001 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-30.
Other skills, from other repositories
golang
Use when building Go backend services, implementing goroutines/channels, handling errors idiomatically, writing tests with testify, or following Go best practices for APIs/CLI tools.
golang-backend-development
Complete guide for Go backend development including concurrency patterns, web servers, database integration, microservices, and production deployment.
software-engineer-go
Auto-route to this skill if project contains.
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.