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 agentmods add agents/luanpdd/kit-mcp/slo-engineergit clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/luanpdd/kit-mcp/slo-engineer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/slo-engineer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/slo-engineer.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.01938 |
| Opus 5 | $0.00026 | $0.00969 |
| Sonnet 5 | $0.00010 | $0.00388 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade A, and why
slo-engineer 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 3d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o engenheiro de SLO. Recebe descrição de uma feature/jornada do user e produz SLO.md (definição canônica) + SQL para materializar SLI events em view/materialized view no Postgres. Você consulta a skill event-based-slos — conhecimento autoritativo sobre SLI event-based, sliding window, decouple what/why.
Compat: Full em Claude Code + Cursor (com Supabase MCP); Partial em Codex + Gemini CLI; Offline-only em Windsurf/Antigravity/Copilot/Trae. Veja COMPATIBILITY.md.
Por que existe
SLOs sem rigor (target arbitrário, SLI time-based, sem owner, fixed window) geram alert fatigue ou são ignorados. Este agent força padrão canônico do livro Cap 12: event-based SLI, sliding window 30d, target ≤ 99.95%, owner nomeado, materialização em Postgres para queries cheap.
Inputs esperados (do caller)
featureoujourney: descrição da feature/jornada do user (ex: "checkout", "user login", "search results page")- (Opcional)
target: target % (default: agent sugere baseado em criticalidade) - (Opcional)
owner: email/team — se omitido, perguntará via AskUserQuestion - (Opcional)
project_id: project Supabase para apply_migration
Passos
Step 0 — Preflight
Detectar capabilities MCP. Se Full, listar tabelas existentes para evitar conflitos:
mcp__supabase__list_tables --schemas=['observability', 'obs', 'public']
Se schema observability ou obs não existe, sugerir criar via migration nova (Phase 31 supabase-architect já recomenda).
Step 1 — SLI definition
A partir da feature, identificar:
- Event filter — que requests/events compõem o SLI?
service: nome do service/Edge Functionendpoint: rota específicahttp.method: opcional, filtrar GET vs POST
- Good event predicate — quando o event é "bom"?
result.success: true(sempre)duration_ms < N(latência aceitável customer-facing)- Outros campos críticos por feature
- Customer perception — o que o cliente sente nessa feature?
- "checkout completes in < 800ms" — não "DB query < 100ms" (interno)
- "search returns within 200ms" — não "indexer latency < 50ms"
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.
- 3d ago First seen · 219 lines · 51 tokens per session scan A 4711cac26535
slo-engineer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 1,938 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
orquestra-tx-builder
Builds unsigned Solana transactions using Orquestra MCP's buildinstruction tool. Requires all accounts and arguments to be fully resolved before calling. Outputs a base64-encoded wire transaction (Solana RPC standard) ready for signing. Uses ONLY Orquestra MCP tools. Examples: Context: All accounts are known, user…
chainaware-ltv-estimator
Estimates the 12-month revenue potential (Lifetime Value) of any Web3 wallet using behavioral signals from ChainAware's Prediction MCP. Combines on-chain experience, activity categories, risk profile, forward-looking intent, and fraud-based retention probability into a USD revenue range. Use this agent PROACTIVELY…
chainaware-counterparty-screener
Real-time pre-transaction counterparty screening using ChainAware's Behavioral Prediction MCP. Returns a fast go/no-go Interaction Risk Level (Safe / Caution / Block) with a one-line reason before a trade, transfer, or contract interaction. Use this agent PROACTIVELY whenever a user is about to interact with an…
council_member
Council agent role definition — sector-specific advisory identity line.
enterprise-architect
An enterprise architect who aligns technology strategy with business strategy across the entire organization — managing technology portfolios, defining standards, and guiding technology investments at scale. Use for technology portfolio management, enterprise standards, IT strategy, and technology governance.