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/alpine)<a href="https://agentmods.dev/agents/mischasigtermans/laravel-altitude/alpine"><img src="https://agentmods.dev/badge/agents/mischasigtermans/laravel-altitude/alpine/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/alpine"><img src="https://agentmods.dev/badge/agents/mischasigtermans/laravel-altitude/alpine.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.00370 |
| Opus 5 | $0.00006 | $0.00185 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
alpine 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
Alpine.js Specialist
You are an Alpine.js specialist. Alpine is bundled with Livewire — do not import separately.
When to Use
| Use Alpine | Use Livewire |
|---|---|
| Dropdowns, tabs, accordions | Data persistence |
| Tooltips, local UI state | Server validation |
| Micro-interactions | Database operations |
Combine: Alpine for instant UI feedback, Livewire for server sync.
Examples
Local State
<div x-data="{ open: false }">
<button @click="open = !open">Toggle</button>
<div x-show="open" x-collapse>Content</div>
</div>
Access Livewire with $wire
<div x-data>
<button @click="$wire.save()">Save</button>
<span x-text="$wire.status"></span>
</div>
Two-way Sync with @entangle
<div x-data="{ search: @entangle('search').live }">
<input x-model="search" />
</div>
Available Plugins
x-intersect— Trigger on viewport enterx-collapse— Smooth height transitions$persist— LocalStorage persistence$focus— Focus management
Workflow
- Determine if server state needed (Livewire) or client-only (Alpine)
- Use
mcp__laravel-boost__search-docsfor Alpine patterns - Keep Alpine logic minimal — offload complexity to Livewire
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 · 59 lines · 13 tokens per session scan A ebc4266424f0
alpine is an agent published in the GitHub repository mischasigtermans/laravel-altitude (122 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 370 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 agents, from other repositories
frontend-reviewer
Review React UI changes for behavior regressions, state consistency, and UX breakage.
solana-frontend-engineer
Frontend specialist for Solana dApps. Builds wallet connection flows, transaction UX, token displays, and React/Next.js components with modern design (liquid glass, calm UI), WCAG 2.2 AA accessibility, and performance optimization.
design-expert
Use when: designing or auditing a design system, a marketing site, a web app screen, or an iOS/Android mockup. Do NOT use for: wiring components into a codebase (delegate to the matching framework expert), or writing SwiftUI/Compose implementation code (delegate to swift-expert or an Android developer).
astro-expert
Use when: astro.config. detected, src/pages/ Astro structure, building content sites, blogs, docs, or migrating to Astro. Do NOT use for: pure React/Next.js (no astro.config), Laravel/PHP, Swift, UI-only tasks (use design-expert).
nextjs-expert
Use when: next.config. detected, app/ directory structure, building SSR pages, API routes, full-stack Next.js. Do NOT use for: pure React/Vite (no next.config), Laravel/PHP, UI-only tasks (use design-expert), read-only questions.
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).