daily loss lock system

    by nowrich

    1

    Architect and deploy automated risk controls, daily loss limits, and shutdown triggers for trading bots.

    Secure checkout via Stripe

    0 installsSecurity scanned

    Works with the AI tools you already use

    CClaude CodeCCursorCCodex CLIGGitHub CopilotGGemini CLI+17 more

    See it in action

    You say

    Design a risk management system for a Python crypto bot with a $500 daily loss limit and a 3-trade max per session. Include a 30-minute cooldown after 2 consecutive losses.

    Your agent does

    I will generate a daily-loss-lock-system configuration.

    Risk Engine Logic:

    • Hard Stop: $500 (Liquidate all + Lock)
    • Trade Limit: 3 round-trips
    • Cooldown: 30m after 2 losses
    • State Store: persistent_risk_state.json

    Validation flow: check lock_active -> check cooldown -> check count -> execute.

    What you get

    Limit daily drawdown to a fixed percentage of account equity.Force cooling-off periods after a series of losing trades.Automate emergency liquidation when hard loss thresholds are breached.Track session-based trade counts to prevent over-trading.

    About this skill

    The problem

    Emotional trading and revenge entries often lead to account-level catastrophes. Developers building trading bots frequently lack deterministic, persistent risk controls that can forcefully stop a strategy before a single bad session wipes out months of gains.

    What it does

    • Enforces hard and soft loss stops based on combined realized and unrealized PnL.
    • Implements trade-count caps and consecutive loss limits to prevent over-trading.
    • Manages mandatory cooldown periods and automated strategy shutdown triggers.
    • Tracks risk state across restarts using persistent JSON storage.
    • Provides a structured execution flow that validates every entry against current risk exposure.

    Frameworks & tools

    Designed for integration with trading bot frameworks using REST/WebSocket APIs. Uses JSON for state persistence and YAML for risk configuration.

    Why this beats prompting it yourself

    Standard prompts often overlook edge cases like partial fills, state persistence across crashes, and unrealized PnL calculation. This skill provides a complete architectural blueprint for a failsafe risk engine, ensuring your bot cannot bypass its own rules during high volatility.

    Use cases

    • Preventing runaway losses during high market volatility.
    • Enforcing discipline for high-frequency trading strategies.
    • Protecting prop firm accounts from violating daily drawdown rules.
    • Automating emergency liquidations during API or data feed failures.

    Known limitations

    Requires a persistent storage layer to track state across session restarts. Does not predict market moves or guarantee profitability.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    Listedtoday

    Frequently Asked Questions

    Popular in Business & Operations