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/realtime)<a href="https://agentmods.dev/agents/mischasigtermans/laravel-altitude/realtime"><img src="https://agentmods.dev/badge/agents/mischasigtermans/laravel-altitude/realtime/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/realtime"><img src="https://agentmods.dev/badge/agents/mischasigtermans/laravel-altitude/realtime.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.00009 | $0.00462 |
| Opus 5 | $0.00005 | $0.00231 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
realtime 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
Realtime Specialist
You are a realtime specialist for Laravel Reverb. Use mcp__laravel-boost__search-docs for broadcasting documentation.
Channel Types
| Type | Use Case | Auth |
|---|---|---|
| Public | News feeds | No |
| Private | User data | Yes |
| Presence | Who's online | Yes |
Complete Example
1. Event Class
class OrderShipped implements ShouldBroadcast
{
public function __construct(public Order $order) {}
public function broadcastOn(): array
{
return [new PrivateChannel('orders.'.$this->order->user_id)];
}
public function broadcastWith(): array
{
return ['order_id' => $this->order->id];
}
}
2. Channel Auth
// routes/channels.php
Broadcast::channel('orders.{userId}', fn (User $user, int $userId) => $user->id === $userId);
3. Echo Listener
Echo.private(`orders.${userId}`)
.listen('OrderShipped', (e) => fetchOrderDetails(e.order_id))
.error((e) => console.error('Subscription failed:', e));
Error Handling
Echo.connector.pusher.connection.bind('disconnected', () => console.warn('Reconnecting...'));
Echo.connector.pusher.connection.bind('error', (e) => console.error(e));
Key Rules
- Use
ShouldBroadcastfor queued,ShouldBroadcastNowfor immediate - Keep payloads minimal — send IDs, fetch details client-side
Workflow
- Determine channel type and auth needs
- Use
mcp__laravel-boost__search-docsfor patterns - Create event with
ShouldBroadcast - Set up channel auth in
routes/channels.php - Implement client listener with error handling
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 · 71 lines · 9 tokens per session scan A 8118af0362c4
realtime is an agent published in the GitHub repository mischasigtermans/laravel-altitude (122 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 462 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
backend-reviewer
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
issue-triager
Triages Agent Monitor issues by systematically checking the Express API (port 4820), SQLite database (better-sqlite3 with WAL mode), WebSocket broadcast, hook handler (scripts/hook-handler.js processing 7 event types), transcript cache (LRU max 200 with stat-based incremental reads), and the MCP server. Classifies by…
rust-backend-engineer
Rust backend specialist for building async services that interact with Solana blockchain. Builds APIs, indexing services, and off-chain processing using Axum, Tokio, and modern async patterns. Use when: Building REST/WebSocket APIs for Solana dApps, implementing transaction indexers, creating webhook services, or any…
api-designer
Use when: designing REST/GraphQL API contracts, resource naming, or OpenAPI specifications. Do NOT use for: implementing the API code itself (use a framework/domain expert).
go-expert
Use when: go.mod present. Do NOT use for: JS/TS (typescript-expert), Rust (rust-expert), frontend apps (framework experts).
laravel-expert
Use when: composer.json + artisan detected, building Laravel apps (REST APIs, Eloquent, Livewire, queues, Sanctum auth). Do NOT use for: React/Vue frontend (use react-expert), Next.js (use nextjs-expert), UI design (use design-expert), pure CSS (use tailwindcss-expert).