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.
git clone --depth 1 https://github.com/muyen/vibe-to-prodWrote 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/commands/muyen/vibe-to-prod/generate-tests)<a href="https://agentmods.dev/commands/muyen/vibe-to-prod/generate-tests"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/generate-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/commands/muyen/vibe-to-prod/generate-tests"><img src="https://agentmods.dev/badge/commands/muyen/vibe-to-prod/generate-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.00013 | $0.00693 |
| Opus 5.5 | $0.00005 | $0.00277 |
| Sonnet 5.5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
generate-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 12d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Tests
Generate tests for: $ARGUMENTS
Detect Platform
Based on the file path, determine which testing framework to use:
Backend (Go)
- File pattern:
backend/**/*.go - Test file:
*_test.goin same directory - Framework: Go testing + testify
iOS (Swift)
- File pattern:
mobile/ios/**/*.swift - Test file:
*Tests.swiftin test directory - Framework: XCTest
Android (Kotlin)
- File pattern:
mobile/android/**/*.kt - Test file:
*Test.ktin test directory - Framework: JUnit + MockK
Backend (Go) Tests
Unit Test Template
package domain_test
import (
"context"
"testing"
"github.com/stretchr/testify/assert"
"github.com/stretchr/testify/require"
)
func TestFunctionName(t *testing.T) {
t.Run("success case", func(t *testing.T) {
// Arrange
ctx := context.Background()
// Act
result, err := FunctionUnderTest(ctx, input)
// Assert
require.NoError(t, err)
assert.Equal(t, expected, result)
})
t.Run("error case", func(t *testing.T) {
// Test error scenarios
})
}
Run Backend Tests
cd backend && go test ./... -v
cd backend && go test ./... -short # Skip integration tests
iOS (Swift) Tests
Unit Test Template
import XCTest
@testable import App
final class ComponentTests: XCTestCase {
var sut: ComponentUnderTest!
override func setUp() {
super.setUp()
sut = ComponentUnderTest()
}
override func tearDown() {
sut = nil
super.tearDown()
}
func testSuccessCase() {
// Arrange
let input = ...
// Act
let result = sut.method(input)
// Assert
XCTAssertEqual(result, expected)
}
}
Android (Kotlin) Tests
Unit Test Template
import org.junit.Test
import org.junit.Assert.*
class ComponentTest {
@Test
fun `success case returns expected result`() {
// Arrange
val sut = ComponentUnderTest()
// Act
val result = sut.method(input)
// Assert
assertEquals(expected, result)
}
}
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.
- 12d ago First seen · 147 lines · 0 tokens per session scan A a8722dde7561
generate-tests is a command published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 693 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-10-04.
Other commands, from other repositories
testing
Comprehensive testing setup for FastAPI applications with pytest and async support.
dare-laravel-api
Padrões DARE para APIs REST em Laravel 11 + PHP 8.3. Strict Types, FormRequests, Services, Resources, Repositories, Eloquent + casts, tratamento global de exceções, testes Pest, PHPStan/Larastan nível 8.
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.