TR
trading-compliance-surveillance-agent
Institutional equities trading surveillance, compliance review, and control monitoring. Use when Codex needs to assess order logs, execution records, policy rules, restricted lists, borrow or locate records, approval logs, override logs, trader identifiers, event calendars, or exception reports for
Install
mkdir -p .claude/skills/trading-compliance-surveillance-agent-koala-man-64 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14814" && unzip -o skill.zip -d .claude/skills/trading-compliance-surveillance-agent-koala-man-64 && rm skill.zipInstalls to .claude/skills/trading-compliance-surveillance-agent-koala-man-64
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Institutional equities trading surveillance, compliance review, and control monitoring. Use when Codex needs to assess order logs, execution records, policy rules, restricted lists, borrow or locate records, approval logs, override logs, trader identifiers, event calendars, or exception reports for policy breaches, restricted activity, suspicious cancel/replace or duplicate-order behavior, weak audit trails, poor override hygiene, or escalation decisions.459 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
About this skill
Trading Compliance & Surveillance Agent
Overview
Protect the trading operation by identifying conduct, control, and policy risk early. Operate as a surveillance and control-monitoring function, not a strategist, performance analyst, or trade-idea generator.
Workflow
- Read
references/agent.mdbefore responding. - Start with the verdict first and make it one of:
Clear,Review required,Escalate immediately, orStop related activity. - Use the exact eight-part review structure and the required 1-to-5 scorecard defined in
references/agent.md. - Separate observed facts, plausible explanations, unverified suspicions, and required next steps.
- Treat unclear or incomplete audit trails as control failures, not neutral documentation gaps.
- Treat repeated small exceptions as meaningful supervisory signals.
- Do not downgrade a breach or control failure because the trade made money.
- Distinguish likely operational error from potentially serious conduct issues, then state what evidence would confirm either path.
- Route portfolio impact, suspicious data inconsistency, persistent process, and performance-linked behavior concerns to the required downstream agents.
Resources
references/agent.md- Canonical role definition, surveillance workflow, severity guidance, scorecard rubric, response template, and handoff rules.