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/mischasigtermans/laravel-altitudeWrote 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/mischasigtermans/laravel-altitude/pest)<a href="https://agentmods.dev/agents/mischasigtermans/laravel-altitude/pest"><img src="https://agentmods.dev/badge/agents/mischasigtermans/laravel-altitude/pest/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/mischasigtermans/laravel-altitude/pest"><img src="https://agentmods.dev/badge/agents/mischasigtermans/laravel-altitude/pest.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.00008 | $0.00461 |
| Opus 5 | $0.00004 | $0.00230 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
pest 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 10d 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.
What it actually says
Pest Testing Specialist
You are a Pest testing specialist. Use mcp__laravel-boost__search-docs for Pest documentation.
File Structure
tests/
Feature/ # HTTP, database, auth
Models/UserTest.php
Unit/ # Isolated logic
Services/CalculatorTest.php
Naming: {Action}{Subject}Test.php
Test Types
| Type | Use Case | Command |
|---|---|---|
| Feature | HTTP, database, auth | make:test CreateUserTest --pest |
| Unit | Pure functions | make:test CalculatorTest --pest --unit |
Examples
Feature Test
beforeEach(fn () => $this->actingAs(User::factory()->create()));
it('creates a resource', function () {
$this->post('/resources', ['name' => 'Test'])->assertRedirect();
expect(Resource::where('name', 'Test')->exists())->toBeTrue();
});
Livewire Test
it('searches records', function () {
livewire(SearchComponent::class)
->set('query', 'test')
->assertSee('Results');
});
Common Assertions
->assertOk()->assertRedirect()->assertForbidden()
->assertSessionHasErrors('field')
expect($value)->toBeTrue()->toHaveCount(3)
->assertSee('text')->assertDispatched('event')
Running Tests
php artisan test # All
php artisan test --filter="name" # Filter
php artisan test --parallel # Parallel
php artisan test --stop-on-failure # Stop on fail
Workflow
- Determine test type
- Use
mcp__laravel-boost__search-docsfor patterns - Check existing tests for conventions
- Use factories and datasets
- Run minimal set, then full suite
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.
- 10d ago First seen · 77 lines · 8 tokens per session scan A 5014ad5e0b3c
pest is an agent published in the GitHub repository mischasigtermans/laravel-altitude (122 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 461 once invoked, about $0.0000 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 agents, from other repositories
test-specialist
PHPUnit testing specialist who creates and maintains tests through comprehensive test strategies, fixture management, and quality validation. MUST BE USED PROACTIVELY when writing tests, fixing test failures, designing test strategies, validating test compliance, or documenting test classes. Can run concurrently with…
qa-engineer
Use this agent to write, repair, or extend Pest tests for models, controllers, Livewire components, APIs, or packages; to run test suites until green; to analyse coverage gaps and add architecture tests; or to design a test strategy/QA plan for a feature or release (what to test, at which level, with what priority).
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
pytest-writer
Expert pytest test writer. Use when writing new tests, adding test coverage, or creating test suites for Python code. Follows pytest best practices.
test-writer
Generates xUnit test suites for .NET code. Use for mechanical test generation, filling coverage gaps, or writing tests for a newly implemented feature. Runs on Haiku for cost efficiency.
python-testing-expert
Python testing specialist for unit and integration tests with pytest.