metalbear-co/mirrord / skills/skills/mirrord-propagation-discovery
mirrord-propagation-discovery
VerifiedScans a live Kubernetes environment with `mirrord dump` to find an identifier mirrord can filter traffic on: a header, a `baggage` or `tracestate` member, a tenant or user id, a trace id (W3C, B3, X-Ray, Google, Jaeger), a JWT claim, a cookie, a path segment, or a JSON body field that is present on every hop of a request chain, unique to one developer's traffic, and settable by that developer. Runs mirror-only dumps on each service, sends a tagged probe request at the edge or observes real traffic, scores the candidates, and produces the matching `http_filter` (regex, jq on headers, path, method, body, or combinations) plus a per-hop report of where each identifier is dropped. Installs the mirrord CLI through a package manager when it is missing. Use when the user asks what to filter on, whether the cluster already propagates a request id or trace context, how to isolate their own requests on a shared staging cluster, how to filter on a JWT or cookie with mirrord, or wants to inspect live traffic with mirrord dump. Changes no application code: propagation gaps go to the mirrord-header-propagation skill.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 3.4 KB |
| SKILL.md | skill md | 17.9 KB |
| references/carriers.md | markdown | 13.9 KB |
| references/filter-recipes.md | markdown | 11.8 KB |
| references/identifier-catalog.md | markdown | 8.2 KB |
| references/reading-dumps.md | markdown | 9.4 KB |
| references/report-template.md | markdown | 4.8 KB |
| scripts/dump_stats.pyexecutable | script | 16.7 KB |
| scripts/request_recorder.pyexecutable | script | 2.1 KB |
README.md
View on GitHub# mirrord-propagation-discovery
Find out what mirrord can filter traffic on in **your** cluster: scan each service's live incoming traffic with `mirrord dump`, check which identifier (a `baggage` member, a correlation-id header, a tenant or user id, a trace id, a JWT claim, a cookie, a path segment, a body field) is present on every hop, unique to one developer, and settable by that developer, and turn it into a `mirrord.json` filter. No application code changes.
## What it does
This skill helps AI agents:
- **Install** the mirrord CLI through a package manager when it is missing (never a piped remote script)
- **Map** the hops of a request flow from the cluster: ingress, services, workloads, ports
- **Dump** every hop at once in mirror mode, send one tagged probe request at the edge (or observe real traffic), and read the output
- **Score** the identifiers found per hop with a stdlib helper: presence, unique-per-request vs stable, probe hits, values shared across hops; JWT claims and `baggage`/`tracestate` members are decoded, secrets are never printed
- **Build** the matching filter: `header_filter` regex, `header_filter_jq` for JWTs and cookies, `path_filter`, `body_filter`, or `all_of`/`any_of` combinations, with `{{ key }}` templating
- **Verify** it in a mirror session on the deepest hop before anyone steals, with a stdlib request recorder as the local process so the copied request causes no duplicate writes
- **Recognise** anything else that travels between hops, from a reference of vendor trace headers, legacy baggage names, auth-proxy identity headers, routing and feature-flag headers, and queue and event carriers
- **Report** what to filter on, which services it covers and which it does not (and why), which hops a dump can't observe (queue consumers, TLS terminated in the pod), a complete runnable `mirrord.json`, and what the `mirrord-header-propagation` skill has to fix. The report is printed and saved as `.mirrord/propagation-discovery.md`
## Example prompts
```
"Which header or token claim can I filter on so I only get my own requests across all our services?"
"Does our staging cluster already propagate a request id or trace context end to end?"
"Run mirrord dump on the gateway, orders and billing services and tell me what survives every hop"
"I want to filter on my user's JWT with mirrord — check that the token reaches the inventory service"
"Our x-request-id filter works on the API but not on the worker behind it — find something that does"
"Can I filter on my tenant id, or on the trace id our tracer propagates, across every hop?"
```
## Prerequisites
- `kubectl` access to a staging or development cluster
- mirrord CLI **3.191.0+** (`mirrord dump` port auto-detection); **3.194.0+** for jq header filters
- A way to send a request at the edge (ingress URL or `kubectl port-forward`) for the active probe; passive observation works without it
- Nothing Team/Enterprise-specific: `mirrord dump` and HTTP filters are open source. Filtering traffic that the pod itself decrypts needs the Operator's HTTPS stealing setup
## Learn more
- [Inspecting live traffic with `mirrord dump`](https://metalbear.com/mirrord/docs/using-mirrord/incoming-traffic/inspect-live-traffic)
- [Filtering incoming traffic](https://metalbear.com/mirrord/docs/using-mirrord/incoming-traffic/filter-incoming-traffic)
- [Stealing HTTPS traffic](https://metalbear.com/mirrord/docs/using-mirrord/incoming-traffic/steal-https)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |