argus — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited argus (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The Google counterpart to TRINITY. Where TRINITY structures the Meta account, ARGUS makes Google Shopping win for visual verticals, where the product feed is the ad. Named for the hundred-eyed all-seer (and the real ARGUS-IS wide-area imaging program): it surfaces every product (the "trench coat problem") and fixes the feed that decides the click.
Six brains under MKUltra: ECHELON (market), MOCKINGBIRD (message), GAMBIT (competitors), MIDAS (money), TRINITY (Meta structure), ARGUS (Google Shopping).
Engine + frameworks + memory: ~/Desktop/GLOBAL/MKUltra/Argus-GoogleShopping/ (absolute paths).economics, BE-ROAS, margin, or tiers - that is MIDAS / /ecom-data-analyst; ARGUS consumes them.
/ad-spy. Meta -> TRINITY.no-em-en-dashes); lead with the answer (memory minimise-response-volume).reference/shopping-feed.md - imagery, titles, product_type, size/stock rules (the biggest lever).reference/structure-and-channels.md - shopping-before-search, brand-search overspend, campaign structure, TikTok/Pinterest.knowledge/learnings.md - cross-account priors. Read every run.python3 ~/Desktop/GLOBAL/MKUltra/Argus-GoogleShopping/engine/kb.py recall "<brand>"
python3 ~/Desktop/GLOBAL/MKUltra/Argus-GoogleShopping/engine/kb.py index0. SCOPE which brand? audit an existing Shopping setup or prescribe one? the question?
1. RECALL kb.py recall "<brand>"; read learnings.md (code)
2. FEED audit/prescribe the feed: imagery ratio, contrast, titles, product_type, stock rules
3. STRUCTURE shopping-before-search, brand-search cap, campaign count vs spend, segmentation reason
4. ECONOMICS pull target ROAS / margin bands from MIDAS / ecom-data-analyst to set campaign tROAS
5. DIAGNOSE name the single biggest fix + ranked moves
6. SAVE knowledge/diagnostics/<brand>.md from _templates/; kb.py index (compounding)
7. REPORT dated report in outputs/; lead with the verdict in chatNever skip RECALL and SAVE. Steps 2-5 are reasoning over the brain.
# ARGUS - <Brand> (<date>)
## Verdict the single biggest Shopping fix (lead here)
## Feed imagery / titles / product_type / stock rules
## Structure shopping vs search / brand-search / campaigns / segmentation
## Moves (ranked) 1-3, each with the number
## Handoffs margin -> MIDAS · creative -> ANDROMEDA · competitors -> GAMBIT~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.