Cogdx Pre Trade Audit

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill's audit-and-trade behavior is mostly disclosed, but it also declares an unexplained scheduled managed automaton around code that can place live trades.

Review or disable the scheduled automaton before installing. Only configure SIMMER_API_KEY if you intend to allow live trading, keep dry-run mode until you have added your own limits or confirmations, and avoid sending secrets in the trade reasoning text.

Findings (5)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

ConcernHigh Confidence
ASI10: Rogue Agents
What this means

The skill may run repeatedly after installation rather than only when you ask it to audit a trade.

Why it was flagged

This declares recurring managed background execution. That persistence is not described in SKILL.md, and it is attached to a financial trading script, making the runtime scope unclear.

Skill content
"cron": "*/15 * * * *", "automaton": { "managed": true, "entrypoint": "cogdx_pre_trade_audit.py" }
Recommendation

Disable or remove the cron/automaton unless you explicitly want scheduled execution, and require per-trade user approval for any live trading.

What this means

If used with live mode, the skill can spend funds or create market positions based on the audit result.

Why it was flagged

The live trade path can mutate a real trading account. It is purpose-aligned and dry-run by default, but users should understand that passing --live can place a real trade.

Skill content
if not live: ... "Dry-run: trade would execute. Pass --live for real trades." ... trade = client.trade(market_id=market_id, side=side, amount=amount, ...)
Recommendation

Use dry-run first, set conservative trade amounts, and add explicit confirmation or budget controls before enabling live trades.

What this means

A configured SIMMER_API_KEY may allow the skill to place trades through the connected provider.

Why it was flagged

The skill uses an environment API key to access a trading provider. This is expected for live trading and is disclosed in SKILL.md, but it is still delegated financial authority.

Skill content
SimmerClient(api_key=os.environ["SIMMER_API_KEY"], venue="polymarket")
Recommendation

Use a limited-scope or low-balance trading key if possible, and do not configure the key unless you intend to use live trading.

What this means

Your private trading rationale and optional wallet header may leave your local environment and be processed by an external service.

Why it was flagged

The user's trade reasoning is sent to the external Cerebratech/CogDx API for analysis. This is disclosed and purpose-aligned, but the trade thesis may be sensitive.

Skill content
requests.post(f"{_cogdx_base_url}/reasoning_trace_analysis", headers=headers, json={"trace": reasoning}, timeout=30)
Recommendation

Avoid including unnecessary secrets or sensitive account details in the reasoning text, and only use the service if you trust the provider.

What this means

Installing or running the skill may pull third-party code that participates in credentialed trading workflows.

Why it was flagged

The skill depends on pip packages without pinned versions. This is common for integrations, but dependency provenance matters because the skill can access a trading API key.

Skill content
"requires": { "pip": ["simmer-sdk", "requests"], "env": ["SIMMER_API_KEY"] }
Recommendation

Verify dependency sources and versions before enabling the skill in an environment with trading credentials.