FD clawback
Mirror congressional stock trades with automated broker execution and risk management
Not recommendedcritical or high security findings · low grade F
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
Dangerous commands
If you install
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
For the author
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Exfiltration medium severity
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
If you install
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
For the author
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 27
-
high Dangerous commands
cmd-persistencescripts/setup_cron.sh:61Persistence mechanism (cron / launchd / scheduled task / autorun registry)EXISTING=$(crontab -l 2>/dev/null | grep -c "run_bot.sh")
-
high Dangerous commands
cmd-persistencescripts/setup_cron.sh:74Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "# Congressional Trade Mirror Bot") | crontab -
-
high Dangerous commands
cmd-persistencescripts/setup_cron.sh:75Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "$DAILY_CHECK") | crontab -
-
high Dangerous commands
cmd-persistencescripts/setup_cron.sh:76Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "$HOURLY_MONITOR") | crontab -
-
high Dangerous commands
cmd-persistencesetup_automated_trading.sh:137Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "# Congressional Trading System - Runs at 9 AM weekdays"; echo "$CRON_JOB") | crontab -
Medium and low: 22
-
medium Exfiltration
exfil-webhook-urlfinal_setup.sh:351Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{token}/sendMessage"quoted -
medium Dangerous commands
cmd-persistencescripts/setup_cron.sh:66Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "run_bot.sh" | crontab -
detector -
medium Dangerous commands
cmd-persistencesetup_automated_trading.sh:133Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)crontab -l 2>/dev/null | grep -v "congressional_trading" | crontab -
detector -
medium Exfiltration
exfil-webhook-urlsrc/congress_data/alert_manager.py:200Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{bot_token}/sendMessage"quoted -
medium Exfiltration
exfil-webhook-urlsrc/notifications.py:20Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)self.base_url = f"https://api.telegram.org/bot{bot_token}"quoted -
medium Exfiltration
exfil-webhook-urlsrc/telegram_notifier.py:33Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{self.bot_token}/sendMessage"quoted -
low Dangerous commands
cmd-cron-mentionAUTOMATED_SYSTEM_SUMMARY.md:147Mentions editing / listing crontabcrontab -e # Remove the congressional_trading line
-
low Dangerous commands
cmd-cron-mentionCONGRESSIONAL_DATA.md:154Mentions editing / listing crontab (quoted — discussed, not commanded)- Check crontab: `crontab -l`
quoted -
low Dangerous commands
cmd-cron-mentiondocs/CONGRESSIONAL_DATA.md:154Mentions editing / listing crontab (quoted — discussed, not commanded)- Check crontab: `crontab -l`
quoted -
low Dangerous commands
cmd-cron-mentionfinal_setup.sh:266Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "congressional_trading"; then
-
low Dangerous commands
cmd-cron-mentionfinal_setup.sh:268Mentions editing / listing crontabcrontab -l 2>/dev/null | grep "congressional_trading" | while read job; do
-
low Dangerous commands
cmd-background-processfinal_setup.sh:309Starts a background / autostarted processnohup ./scripts/run_bot.sh full > logs/startup.log 2>&1 &
-
low Dangerous commands
cmd-cron-mentionscripts/setup_cron.sh:58Mentions editing / listing crontabcrontab -l > /tmp/crontab_backup_$(date +%Y%m%d_%H%M%S).txt 2>/dev/null
-
low Dangerous commands
cmd-cron-mentionscripts/setup_cron.sh:61Mentions editing / listing crontabEXISTING=$(crontab -l 2>/dev/null | grep -c "run_bot.sh")
-
low Dangerous commands
cmd-cron-mentionscripts/setup_cron.sh:66Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "run_bot.sh" | crontab -
-
low Dangerous commands
cmd-cron-mentionscripts/setup_cron.sh:74Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "# Congressional Trade Mirror Bot") | crontab -
-
low Dangerous commands
cmd-cron-mentionscripts/setup_cron.sh:75Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "$DAILY_CHECK") | crontab -
-
low Dangerous commands
cmd-cron-mentionsetup_automated_trading.sh:131Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "congressional_trading"; then
-
low Dangerous commands
cmd-cron-mentionsetup_automated_trading.sh:133Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "congressional_trading" | crontab -
-
low Dangerous commands
cmd-cron-mentionsetup_automated_trading.sh:137Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "# Congressional Trading System - Runs at 9 AM weekdays"; echo "$CRON_JOB") | crontab -
-
low Dangerous commands
cmd-cron-mentionsetup_automated_trading.sh:142Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -A2 -B2 "congressional_trading"
-
low Dangerous commands
cmd-cron-mentionsetup_automated_trading.sh:219Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "congressional_trading"; then
Files scanned: 49. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (clawback) differs from the folder (etrade-pelosi-bot)
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 1167 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 85: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (7 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This skill can place real brokerage trades and persist credentials locally, but its safeguards and disclosures are not strong enough for unattended financial automation.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026