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/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/commands/luanpdd/kit-mcp/load-shedding)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/load-shedding"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/load-shedding.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.1 | $0.00043 | $0.01156 |
| Opus 5 | $0.00022 | $0.00578 |
| Sonnet 5 | $0.00009 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
load-shedding 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 4d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cria/Atualiza:
- Patches no
target_path supabase/functions/_shared/load-shedder.ts(se não existe)supabase/functions/_shared/token-bucket.ts(se rate-limit aplicado)
Após: handler retorna 503 + Retry-After quando saturated, em vez de aceitar e cair. Defesa central contra cascade.
Exemplos:
/load-shedding supabase/functions/process-orders/index.ts
/load-shedding src/handlers/webhook.ts --max-concurrent 500
/load-shedding supabase/functions/api/index.ts --patterns concurrency-limit,deadline-aware
1. Parsear argumentos
TARGET_PATH=$(echo "$ARGUMENTS" | awk '{print $1}')
MAX_CONCURRENT=$(echo "$ARGUMENTS" | grep -oE -- '--max-concurrent [0-9]+' | awk '{print $2}')
QUEUE_MAX_SIZE=$(echo "$ARGUMENTS" | grep -oE -- '--queue-max-size [0-9]+' | awk '{print $2}')
PATTERNS=$(echo "$ARGUMENTS" | grep -oE -- '--patterns [^ ]+' | awk '{print $2}')
[ -z "$MAX_CONCURRENT" ] && MAX_CONCURRENT=1000
[ -z "$QUEUE_MAX_SIZE" ] && QUEUE_MAX_SIZE=10000
if [ -z "$TARGET_PATH" ]; then
echo "ERROR: target_path obrigatório"
exit 1
fi
[ ! -f "$TARGET_PATH" ] && { echo "ERROR: arquivo não encontrado"; exit 1; }
2. Dispatch para load-shedding-instrumenter
Task(
subagent_type="load-shedding-instrumenter",
prompt="
target_path: ${TARGET_PATH}
max_concurrent: ${MAX_CONCURRENT}
queue_max_size: ${QUEUE_MAX_SIZE}
${PATTERNS:+patterns: ${PATTERNS}}
Aplicar skill load-shedding-graceful-degradation. Patches:
1. Concurrency limit + 503 graceful (LoadShedder em _shared)
2. Deadline-aware handler (x-deadline-ms header parsing)
3. Queue bound + drop oldest (FIFO drop)
4. Server-side rate limit (token bucket per-client)
5. Slow start state machine (5 min ramp em recovery)
Verify compilação verde após patches. Output curto com lista de patches aplicados.
"
)
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.
- 4d ago First seen · 118 lines · 43 tokens per session scan A 4e339d5c6821
load-shedding is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,156 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-03.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…