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 OpenLAIR/OpenSkill --skill evo-azure-bgp-oscillation-route-leakgit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-azure-bgp-oscillation-route-leak)<a href="https://agentmods.dev/skills/openlair/openskill/evo-azure-bgp-oscillation-route-leak"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-azure-bgp-oscillation-route-leak/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/openlair/openskill/evo-azure-bgp-oscillation-route-leak"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-azure-bgp-oscillation-route-leak.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.00059 | $0.00703 |
| Opus 5.5 | $0.00024 | $0.00281 |
| Sonnet 5.5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
evo-azure-bgp-oscillation-route-leak 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BGP Route Oscillation and Route Leak Analyzer for Azure Virtual WAN
Detects BGP route oscillation and valley-free route leak violations in Azure Virtual WAN multi-hub topologies, then evaluates whether proposed solutions resolve each issue.
Domain Knowledge
Oscillation Detection (Preference Cycle)
A BGP oscillation occurs when ASes form a mutual routing preference cycle: e.g., AS A prefers routes via AS B, while AS B prefers routes via AS A. The preference graph is a directed functional graph (out-degree ≤ 1 per node). A cycle of any length causes persistent non-convergence. Detection uses DFS-based traversal with path tracking.
Output: oscillation_cycle and affected_ases are deterministically ordered (rotated so the smallest ASN appears first).
Route Leak Detection (Gao-Rexford Valley-Free Model)
Under the Gao-Rexford valley-free routing principle (RFC 7908):
- Customer-learned routes → may export to anyone (customers, peers, providers)
- Peer-learned routes → may export to customers ONLY
- Provider-learned routes → may export to customers ONLY
A route leak = exporting peer-learned or provider-learned routes to a peer or provider.
Solution Evaluation Rules
Fixes OSCILLATION:
- Explicitly stop one cycle participant from preferring the other (
stop preferring routes via) - Route preference hierarchy that deprioritizes peer routes (breaks cycle edge)
- Export policy filtering peer-learned routes between cycle participants
- Data-plane override: UDR or Routing Intent
Fixes ROUTE LEAK:
- Export policy blocking provider-learned routes to peers (source-side)
- BGP community no-export on provider routes (source-side)
- Ingress filtering rejecting routes with provider AS in path (receiver-side)
- RPKI origin validation (receiver-side)
- Data-plane override: UDR or Routing Intent
Fixes BOTH: UDR and Routing Intent (forwarding layer overrides)
Fixes NEITHER:
- Timer tuning (keepalive/holdtime), route dampening, ECMP, max-prefix limits
- Waiting for convergence, restarting BGP, prefix-list filtering
- Generic AS-PATH/MED heuristics, generic route maps without specific config
- Disabling BGP sessions / shutting down peering / removing gateways (connectivity destruction — not acceptable)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 61 lines · 59 tokens per session scan A 1a554fc0f2b6
evo-azure-bgp-oscillation-route-leak is a skill published in the GitHub repository OpenLAIR/OpenSkill (97 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 703 once invoked, about $0.0002 per session on Opus 5.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-11.
Other skills, from other repositories
application-integration-troubleshooting
Diagnoses failed, stuck, or silent Google Cloud Application Integration runs and Integration Connectors tasks using the REST API, Cloud Logging, and Cloud Monitoring. Use when an integration fails, returns HTTP 200 without doing the expected work, hangs in a suspended or retry state, or hits IAM, run-as service…
gke-ai-troubleshooting-tpu-mxla-hang
Diagnose GKE Cloud TPU multi-slice training hangs (Megascale HANGDETECTED logs and hang monitored events) using the ML Diagnostics Megascale XLA (MXLA) Hang Analyzer (gcloud alpha mldiagnostics monitored-events) and 1-minute Cloud Monitoring multi-slice latency metrics (kubernetes.io/container/multislice/).…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-node-unresponsive-timeout
Diagnose and mitigate GKE TPU or GPU nodes stuck in NotReady / NodeStatusUnknown ("Kubelet stopped posting node status") due to host kernel panics, hardware lockups, or disabled node auto-repair. Use when nodes stop heartbeating beyond the node auto-repair threshold and pods remain stuck in Terminating. Don't use for…
gke-ai-troubleshooting-tpu-performance-degradation
Diagnose GKE Cloud TPU training throughput drops and step-time regressions (15%+ TPU duty-cycle drop) using ML Diagnostics Workload Monitoring (gcloud alpha mldiagnostics monitored-events / hypercomputecluster.googleapis.com/v1alpha) and 1-minute Cloud Monitoring system metrics (kubernetes.io/node/accelerator/).…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.