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/onsi/gomega/overviewnpx skills add onsi/gomega --skill overviewgit clone --depth 1 https://github.com/onsi/gomegaWrote 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/onsi/gomega/overview)<a href="https://agentmods.dev/skills/onsi/gomega/overview"><img src="https://agentmods.dev/badge/skills/onsi/gomega/overview.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 | $0.00104 | $0.01229 |
| Opus 5 | $0.00052 | $0.00615 |
| Sonnet 5 | $0.00021 | $0.00246 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
overview 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gomega: the mental model
Gomega is a matcher/assertion library for Go. It pairs best with the Ginkgo test framework but works with any Go test. The canonical narrative docs at https://onsi.github.io/gomega/ are the source of truth; this skill is the orientation and the other skills go deep.
Conventionally you dot-import Gomega so Expect, Equal, Eventually, etc. are unqualified:
import (
. "github.com/onsi/gomega"
. "github.com/onsi/ginkgo/v2" // if using Ginkgo
)
The shape of every assertion
Expect(ACTUAL).To(MATCHER) // Expect(x).To(Equal(3))
Expect(ACTUAL).NotTo(MATCHER)
ACTUAL(left) is anything — the value under test.MATCHER(right) must satisfy theGomegaMatcherinterface. Gomega's matchers (Equal(3),HaveLen(2), …) are just functions that return a matcher value — so you can store, pass, and compose them. →gomega:matchers,gomega:composing-matchers.Ω(ACTUAL).Should(MATCHER)/.ShouldNot(...)is the exact equivalent in theΩnotation (⌥zon macOS).To/ShouldandNotTo/ToNot/ShouldNotare interchangeable syntactic sugar — pick one notation and stay consistent.
Three things to internalize
1. The multi-return error idiom. Expect/Ω accept multiple arguments; the match runs against the first, and fails unless all later arguments are nil/zero. This collapses Go's (value, error) pattern:
Expect(DoSomethingHard()).To(Equal("foo")) // passes only if return is ("foo", nil)
Expect(DoSomethingSimple()).To(Succeed()) // for funcs returning only error
Use .Error() to assert on the trailing error of a multi-return func while ignoring the rest. → gomega:assertions.
2. Failures go through a fail handler. Gomega calls a registered handler on failure. With Ginkgo, RegisterFailHandler(Fail) (auto-generated by ginkgo bootstrap). With plain testing, use g := NewWithT(t) and call g.Expect(...). → gomega:assertions.
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 · 66 lines · 104 tokens per session scan A f2de6ca400ee
overview is a skill published in the GitHub repository onsi/gomega (2,356 stars, last pushed 7d ago), licensed MIT. It adds 104 tokens to every session and 1,229 once invoked, about $0.0005 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
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
video-production
Produce programmable videos with Remotion using scene planning, asset orchestration, and validation gates for automated, brand-consistent video content.