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 commands/kuadrant/mcp-gateway/controller-testsgit clone --depth 1 https://github.com/Kuadrant/mcp-gatewayWhat 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.00018 | $0.01189 |
| Opus 5 | $0.00009 | $0.00594 |
| Sonnet 5 | $0.00004 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
controller-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 2d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When invoked:
Context
You are writing integration tests for Kubernetes controllers using:
- envtest: Provides a real API server for testing without a full cluster
- Ginkgo v2: BDD testing framework
- Gomega: Assertion library with Eventually/Consistently for async checks
Workflow
-
Analyze the controller: Read the controller file specified in $ARGUMENTS (default: look for
*_controller.gofiles ininternal/controller/) -
Check existing tests: Read the corresponding
*_controller_test.gofile andsuite_test.goto understand:- How the test suite is set up (manager, clients, field indexes)
- Existing test patterns and helpers
- Build tags used (e.g.,
//go:build integration)
-
Identify test gaps: Based on the controller's Reconcile logic, identify untested scenarios:
- Happy path reconciliation
- Finalizer add/remove
- Status condition updates
- Cross-namespace references (ReferenceGrant)
- Conflict detection
- Error handling paths
-
Write tests following these patterns:
Timeout Constants
Define timeout constants at the package or file level:
const (
TestTimeout = 10 * time.Second
TestRetryInterval = 100 * time.Millisecond
)
Test Structure
Context("When <scenario>", func() {
// Constants for this context
const resourceName = "test-<scenario>-resource"
// Typed names
typeNamespacedName := types.NamespacedName{
Name: resourceName,
Namespace: "default",
}
// Helper functions
BeforeEach(func() {
createTestGateway(ctx, gatewayName, "default")
createTestMCPGatewayExtension(ctx, resourceName, "default", gatewayName, "default")
})
AfterEach(func() {
deleteTestMCPGatewayExtension(ctx, resourceName, "default")
deleteTestGateway(ctx, gatewayName, "default")
})
It("should <expected behavior>", func() {
// Test body
})
})
Cache Synchronization Pattern
When using a manager's cached client, always wait for cache sync before reconciling:
// Wait for cache to see the resource before reconciling
Eventually(func(g Gomega) {
cached := &v1alpha1.MyResource{}
g.Expect(testIndexedClient.Get(ctx, namespacedName, cached)).To(Succeed())
}, TestTimeout, TestRetryInterval).Should(Succeed())
_, err := reconciler.Reconcile(ctx, reconcile.Request{
NamespacedName: namespacedName,
})
Expect(err).NotTo(HaveOccurred())
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.
- 2d ago First seen · 157 lines · 18 tokens per session scan A e8fcaa2626e7
controller-tests is a command published in the GitHub repository Kuadrant/mcp-gateway (97 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,189 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.