More screenshots
Works with the AI Agents you already use
Repair FastAPI Middleware Request ID Leakage
Fix request correlation IDs leaking across concurrent requests.
$1
Repair FastAPI Middleware Request ID Leakage
Example session with this skill installed
Concurrent async requests inherit one task-context request identifier.
Available evidence: FastAPI request traces (partial). Additional evidence requested: reference policy or configuration, event and change timeline, owner review or test record. Review this case; identify evidence gaps; do not invent a live test or production action.
- Read your context and instructions
- Compiled the repair fastapi middleware
Repair FastAPI Middleware Request ID Leakage — EVIDENCE-LIMITED REVIEW
Scenario received
Concurrent async requests inherit one task-context request identifier.
Source register
- S1: FastAPI request traces — PARTIAL SOURCE PROVIDED.
- S2: reference policy or configuration — NOT PROVIDED; REQUIRED TO VERIFY.
- S3: event and change timeline — NOT PROVIDED; REQUIRED TO VERIFY.
- S4: owner review or test record — NOT PROVIDED; REQUIRED TO VERIFY.
Concrete checks
- Correlate FastAPI request traces with the authorized baseline — AWAITING CORROBORATING EVIDENCE.
- Isolate cross-request context variable reuse using matching identifiers — AWAITING CORROBORATING EVIDENCE.
- Cross-check timestamps, versions and source ownership — AWAITING CORROBORATING EVIDENCE.
- Prepare reversible checks for isolated request correlation plan — AWAITING CORROBORATING EVIDENCE.
Deliverables / acceptance gates
- FastAPI request traces traceability map: DRAFT / INCOMPLETE until evidence is validated.
- cross-request context variable reuse exception register: DRAFT / INCOMPLETE until evidence is validated.
- isolated request correlation plan validation plan: DRAFT / INCOMPLETE until evidence is validated.
Decision
INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair FastAPI Middleware Request ID Leakage is a ToolForge Labs Cursor Skill workflow. Fix request correlation IDs leaking across concurrent requests.
What this skill checks
- Correlate FastAPI request traces with the authorized baseline.
- Isolate cross-request context variable reuse using matching identifiers.
- Cross-check timestamps, versions and source ownership.
- Prepare reversible checks for isolated request correlation plan.
What to provide
- FastAPI request traces.
- reference policy or configuration.
- event and change timeline.
- owner review or test record.
Deliverables
- FastAPI request traces traceability map.
- cross-request context variable reuse exception register.
- isolated request correlation plan validation plan.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago
Permissions
Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.