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 makifbaysal/tasktrooper --skill mockery-suite-testsgit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/mockery-suite-tests)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/mockery-suite-tests"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/mockery-suite-tests/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/makifbaysal/tasktrooper/mockery-suite-tests"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/mockery-suite-tests.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.00063 | $0.01457 |
| Opus 5.5 | $0.00025 | $0.00583 |
| Sonnet 5.5 | $0.00013 | $0.00291 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
mockery-suite-tests 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Test Doubles & Table Tests
Overview
Table-driven tests and real-Postgres repository-adapter tests are non-negotiable everywhere. How test doubles are produced is not: follow the repository's own convention (rule repo-conventions-win) rather than importing Mockery into a repo that hand-writes testify mocks or uses gomock.
Core principle: multi-case behaviour is a table; a repository adapter test runs against real Postgres, never a mocked driver; mocks exist only at port boundaries.
Detect the repo's mocking approach first
ls .mockery.y*ml 2>/dev/null
grep -rlE 'Code generated by mockery|go.uber.org/mock' --include='*.go' . | head -3
.mockery.ymlor files headed "Code generated by mockery" → Mockery v3: regenerate, don't hand-edit (see below).go.uber.org/mockimports → gomock: regenerate withmockgenper the repo'sgo:generatedirective, don't hand-edit.- Neither, but a test file defines
type mockFoo structimplementing a port → the repo hand-writes testify mocks (or fakes). Follow that style; do not introduce a generator the repo doesn't already have. TaskTrooper's own server does exactly this (server/internal/port/mocks/llm_client.go).
Mockery v3 (when the repo already uses it)
- Mocks come from the port interfaces, generated by Mockery v3. Names and location come from
.mockery.yml; v3's defaults areMock<Interface>inmocks_test.goinside the source package, constructorNewMock<Interface>(t)— don't assume a different naming scheme without checking the config. - Regenerate with the repo's own command (
mockery,go generate ./..., ormake mocks) — never hand-edit a generated mock. - Install Mockery from a pinned release binary (GitHub Releases, any OS) or
brew install mockeryon macOS; the project's own docs say not togo install mockery@latest. - A v2
.mockery.yamlmigrates withmockery migrate; don't hand-port the config. - v3 generates an
expecterAPI — use the typedEXPECT()methods, not rawOn("MethodName", ...)string calls, so a renamed method breaks compilation instead of silently passing.
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.
- 5d ago Changed ce1ee42a946c
- 8d ago First seen · 106 lines · 63 tokens per session scan A 67aa501e3c9f
mockery-suite-tests is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 1,457 once invoked, about $0.0003 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-10-05.
Other skills, from other repositories
go-add-test
Add unit/integration tests to a GOB Go microservice following established project patterns. Triggers: "add test", "add tests", "criar teste", "novo teste", "test coverage", "testar", "write tests for", "escrever testes para".
golang-testing-patterns
Modern Go testing patterns including table-driven tests, subtests, test organization, and best practices. Use when writing or refactoring tests, implementing test coverage, or when the user asks about Go testing approaches.
go-development
CIEL's framework for idiomatic Go development, table-driven testing, and performance benchmarking.
golang-testing
Provides a comprehensive guide for writing production-ready Golang tests. Covers table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use whenever writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Essential for testify assertions, mock expectations, argument matchers, call…
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.