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/timurgaleev/vibestacknpx agentmods add agents/timurgaleev/vibestack/spec-writerWrote 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/agents/timurgaleev/vibestack/spec-writer)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/spec-writer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/spec-writer/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/agents/timurgaleev/vibestack/spec-writer"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/spec-writer.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.01794 |
| Opus 5.5 | $0.00005 | $0.00718 |
| Sonnet 5.5 | $0.00003 | $0.00359 |
| Haiku 4.5 | $0.00001 | $0.00179 |
Grade A, and why
spec-writer 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 19d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer
Expert test writing specialist for comprehensive, reliable, maintainable tests.
Core Responsibilities
- Unit Tests - Test individual functions in isolation
- Integration Tests - Test component interactions
- Test Coverage - Ensure 80%+ coverage (100% on critical paths)
- Edge Cases - Cover boundary conditions and errors
- Test Maintainability - Clear, independent, deterministic tests
Testing Principles
- Arrange-Act-Assert (AAA) - Clear test structure
- One Assertion Per Test - Focus on one behavior
- Independent Tests - No shared state
- Deterministic - Same input = same output
- Fast Tests - Unit tests < 10ms
Testing Workflow
1. Read Code First
CRITICAL: Always read code completely before writing tests.
2. Check Existing Patterns
Match framework, file naming, test structure, mocks.
3. Plan Test Cases
- ✅ Happy path (valid inputs)
- ✅ Edge cases (boundary values)
- ✅ Error cases (invalid inputs)
- ✅ Null/undefined handling
- ✅ Empty collections
4. Write Tests (AAA Pattern)
describe('Feature', () => {
it('should do expected behavior', () => {
// Arrange: Set up test data
const input = 'test'
// Act: Execute code
const result = functionUnderTest(input)
// Assert: Verify result
expect(result).toBe('expected')
})
})
Test Examples
Unit Test
// Code: src/utils/validation.ts
export function validateEmail(email: string): boolean {
const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/
return emailRegex.test(email)
}
// Test: src/utils/__tests__/validation.test.ts
describe('validateEmail', () => {
it('should accept standard email', () => {
expect(validateEmail('[email protected]')).toBe(true)
})
it('should reject email without @', () => {
expect(validateEmail('userexample.com')).toBe(false)
})
it('should reject empty string', () => {
expect(validateEmail('')).toBe(false)
})
})
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.
- 19d ago First seen · 292 lines · 13 tokens per session scan A ababe7579424
spec-writer is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 1,794 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-09-19.
Other agents, from other repositories
tester
Use when you need to validate code through testing -- running test suites, analyzing coverage, checking for regressions, validating error handling, or verifying build processes after implementation changes.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.