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 m3taz-ahmed/ai-globals --skill laravel-testing-lordgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/laravel-testing-lord)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/laravel-testing-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/laravel-testing-lord/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/m3taz-ahmed/ai-globals/laravel-testing-lord"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/laravel-testing-lord.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.00042 | $0.01120 |
| Opus 5 | $0.00021 | $0.00560 |
| Sonnet 5 | $0.00008 | $0.00224 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
laravel-testing-lord 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 today.
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
Laravel Testing Lord
[OBJ] Mastery of testing for Laravel 13 + Filament v5 — Pest 3+, feature tests, Filament resource tests, API tests, database tests, and CI/CD integration.
[RULES]
- [CMD] Query Context7 for Pest 3+ and Laravel testing docs. Use
/pestphp/pestand/laravel/frameworklibrary IDs. - [REQ] Pest 3+: Use Pest 3+ for all backend tests.
describe()blocks for grouping.it()for test cases. AAA pattern (Arrange-Act-Assert). One behavior per test. - [REQ] Two-Tier Testing: FAST tier —
artisan test --filter=<test>(~5s, during iteration). FULL tier —artisan test(complete suite + coverage, before done). NEVER run full suite on every change. - [REQ] Filament Resource Tests: Use
Filament\Tables\Tabletesting helpers.->canSeeRecord()/->cannotSeeRecord(). TestActionvisibility via policy. Test form validation via->fillForm()+->assertHasFormErrors(). - [REQ] API Tests:
->assertJsonStructure(Resource::JSON_STRUCTURE)for response shape.->assertJsonPath()for specific values. Test all CRUD operations. Test API versioning viaX-Api-Versionheader. NEVER test without authentication context. - [REQ] Database Tests:
RefreshDatabasetrait for test isolation.Database\Factoriesfor test data. NEVER hardcoded IDs or dates. UseModel::factory()->create()for test data. Test constraints (foreign keys, unique, not null). - [REQ] Coverage: 80% logic, 90% API, 70% total. Use
--coveragein FULL tier.XDEBUG_MODE=coveragefor accurate coverage. NEVER declare done without coverage report. - [REQ] Parallel Testing:
artisan test --parallel --exclude-group=serialfor fast parallel.--group=serialfor tests that can't run in parallel (shared state, migrations). SQLite for fast tier, MySQL/PG for FULL tier. - [REQ] Mocking: Mock external services (
Http::fake(),Queue::fake(),Event::fake()). UseFakePlusLicenseServicepattern for swappable implementations. NEVER mock Eloquent models — use factories + in-memory DB. - [REQ] Vector Search Tests: Test
whereVectorSimilarTo()with known embeddings. TestAsVectorcast round-trip (set array → get array). Test MariaDB binary format vs PG JSON text. Mock embedding API in tests. - [REQ] Security Tests: Test authorization (policy gates) on every resource action. Test input validation (FormRequest). Test SQL injection prevention. Test XSS prevention. Test CSRF tokens. NEVER skip auth tests.
- [REQ] Browser Testing:
pestphp/pest-plugin-browserfor E2E. Test critical user flows (login, CRUD, admin panel). UseLaravel\Duskfor JavaScript-dependent tests. NEVER rely only on unit tests for UI. - [REQ] CI/CD: Run FULL tier in CI.
--parallelfor speed. Upload coverage report. Fail on < 70% total. NEVER merge without green CI.
[WORKFLOWS]
- Test a Filament Resource: Create
tests/Filament/Resources/UserResourceTest.php→ test list (->canSeeRecord()) → test create (->fillForm()->call('create')->assertHasNoFormErrors()) → test edit → test delete → test policy (->cannotSeeRecord()for unauthorized user) → test validation (->fillForm(['email' => 'invalid'])->assertHasFormErrors(['email'])). - Test an API Endpoint: Create
tests/Feature/Api/UserApiTest.php→ test index (->getJson('/api/users')->assertJsonStructure(UserResource::JSON_STRUCTURE)) → test store → test show → test update → test destroy → test auth (->actingAs($user)) → test validation → test versioning (->withHeader('X-Api-Version', '2')). - Test Vector Search: Create
tests/Feature/VectorSearchTest.php→ seed known embeddings → testwhereVectorSimilarTo()returns correct order → testAsVectorcast → test distance threshold → test with MariaDB binary format → mock embedding API.
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.
- today First seen · 51 lines · 42 tokens per session scan A 8a175115e310
laravel-testing-lord is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,120 once invoked, about $0.0002 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-09-12.
Other skills, from other repositories
sync-new-data-type
Adds scaffolding for a new Sync data type in Chromium across protocol buffers, DataType definitions, feature flags, controller builders, unit tests, and metrics.
generate-testability-wrappers
DO NOT USE when the target already consumes an injected interface or built-in abstraction such as IFileSystem or TimeProvider, even if the request says "generate a wrapper"; no new wrapper is needed. Use only when C# source calls an ambient/static dependency and no injectable seam exists: first-time TimeProvider…
convex-test
Generate convex-test tests for the app's Convex functions.
platform-apex-test-generate
Generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking strategies, assertion best practices, and disciplined test-fix loops. Use this skill when creating new Apex test classes, improving test coverage, debugging and fixing failing Apex tests, running test execution…
platform-apex-test-run
Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with Test.cls / Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches Test.cls / Test.cls…
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.