kill-switch-controls

Manage kill switch controls for quantitative trading systems with Python diagnostics.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/GhostOf0days/codex-quant-skills --skill kill-switch-controls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kill-switch-controls
Source: https://github.com/GhostOf0days/codex-quant-skills/tree/main/kill-switch-controls
Command: npx skills add https://github.com/GhostOf0days/codex-quant-skills --skill kill-switch-controls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for robust kill switch controls in production trading systems, ensuring safety, reproducibility, and auditable compliance.

Core Features & Use Cases

  • Risk Management: Define and enforce risk appetite, limits, and escalation rules.
  • Exposure Aggregation & Measurement: Consolidate exposures and measure PnL, tail risk, and scenario outcomes.
  • Incident Response: Investigate breaches with root-cause analysis and remediation.
  • Use Case: Implement automated blocking paths for intraday limit breaches in a live trading environment to prevent significant financial losses.

Quick Start

Run the kill switch controls diagnostics script with your input data.

Frequently Asked Questions about kill-switch-controls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a kill switch for production trading systems?

To implement a kill switch for production trading systems, use this Skill to define risk appetite, aggregate exposures, measure PnL, and establish auditable approval paths with rollback procedures via deterministic Python diagnostics.

What is a kill switch in quantitative research and risk management?

A kill switch in quantitative research and risk management is an automated control mechanism that enforces risk limits, investigates breaches through root-cause analysis, and blocks intraday trading paths to prevent significant financial losses.

How do you investigate intraday limit breaches in a live trading environment?

You investigate intraday limit breaches by applying domain-specific checklists to perform root-cause analysis, measure tail risk and PnL outcomes, and execute remediation steps to secure the live trading environment.

Can I use Python scripts to automate exposure aggregation and risk measurement?

Yes, you can use Python scripts to automate exposure aggregation and risk measurement, running deterministic diagnostics that consolidate exposures, calculate PnL, and evaluate scenario outcomes for compliance.

Does this kill switch approach support auditable production approval with rollback procedures?

Yes, this kill switch approach supports auditable production approval by requiring deterministic diagnostics and domain-specific checklists, facilitating controlled approval workflows and rollback procedures for implementation compliance.

What are the limitations of using automated blocking paths for risk management in trading systems?

Automated blocking paths for risk management require deterministic diagnostics to function correctly, meaning ambiguous input data or incomplete domain-specific checklists can limit the effectiveness of breach investigation and rollback procedures.