Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitnpx agentmods add skills/random6913/claude-code-superkit/benchmarkWrote 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/random6913/claude-code-superkit/benchmark)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/benchmark"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/benchmark/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/random6913/claude-code-superkit/benchmark"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/benchmark.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00771 |
| Opus 5.5 | $0.00006 | $0.00308 |
| Sonnet 5.5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
benchmark 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 today.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Benchmark Runner
Read applicable AGENTS.md instructions and discover available command/file tools. Benchmarks execute project code: inspect setup and side effects, confirm the selected target is authorized, and report missing prerequisites instead of starting services or installing tools implicitly.
Step 1: Detect Project
- Locate the relevant
go.modand configured benchmark commands. If absent, report "No Go project detected" and stop. - Find benchmark functions in the selected module's test files (for example, with
rg). Inspect their dependencies and setup. - If none exist, report "No benchmark functions found" and stop; do not invent results.
Step 2: Parse the Request
- No target: use the project's configured default; otherwise name the package with the most discovered benchmark functions as the selected scope.
- Package target: resolve and validate the requested package/pattern within the intended module.
--compare <ref>: compare the current declared source state with a validated commit/ref.
Treat request text as data, not shell syntax. Record source revision and relevant dirty changes, Go version, OS/architecture, CPU and benchmark flags/environment so results can be interpreted.
Step 3: Run Benchmarks
Use the project's configured command when present. A standalone example is:
go test -run='^$' -bench=. -benchmem -count=6 -timeout=10m ./package/...
Replace the package with the verified scope. -run='^$' excludes ordinary tests; package initialization and TestMain may still run. Preserve command exit and full output in a unique task-owned result directory, not a shared /tmp/bench-new.txt. A timeout, compilation failure or no matched benchmarks is incomplete evidence. Record samples rather than inventing an average or claiming six repetitions guarantee statistical significance.
Step 4: Compare (if requested)
- Resolve the comparison ref to a commit and verify the same benchmark cases/flags can run there.
- Use an isolated checkout through the environment's supported worktree mechanism, or a separate temporary checkout when appropriate. Keep the current branch, index, uncommitted files and stash unchanged; do not stash/switch/reset the user's checkout for comparison.
- Run baseline and current measurements under comparable toolchain, hardware, dependency and load conditions. State differing cases or environments; an added/changed benchmark body may not support a direct performance claim.
- Save baseline and current raw outputs separately with their revision identities and exits. If isolated execution is unavailable, report comparison blocked rather than modifying the original checkout.
- Use an installed
benchstatversion with the two result files and preserve its output. If absent, report raw measurements and unavailable statistical comparison; installing the latest tool is a separate authorized dependency change. - Clean up only the disposable checkout created for this task through its supported lifecycle, after preserving result files and ensuring it contains no user work.
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.
- today Changed · -15 lines · +3 tokens per session e85a8bf4e045
- 1mo ago First seen · 65 lines · 11 tokens per session scan A 096eeb3893b9
benchmark is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 771 once invoked, about $0.0001 per session on Opus 5.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
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
golang-rules
Go coding rules: style, patterns, security, testing. Triggers: .go, go.mod, go.sum, Gin, Echo, Gorilla, testing, gofmt.
api-development
Guidelines for building clean, scalable APIs with Go standard library and NestJS TypeScript, covering security, validation, and modular architecture.
go-ops
Go development patterns, concurrency, error handling, testing, and project structure. Use for: golang, go, goroutine, channel, context, errgroup, go test, go mod, go build, interface, generics, table-driven tests, worker pool, sync.Mutex, sync.WaitGroup, pprof, go vet, golangci-lint, go workspace, functional options…