Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ivanovzlatan2/data-arsenal-v1Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ivanovzlatan2/data-arsenal-v1/ga4-setup)<a href="https://agentmods.dev/commands/ivanovzlatan2/data-arsenal-v1/ga4-setup"><img src="https://agentmods.dev/badge/commands/ivanovzlatan2/data-arsenal-v1/ga4-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ivanovzlatan2/data-arsenal-v1/ga4-setup"><img src="https://agentmods.dev/badge/commands/ivanovzlatan2/data-arsenal-v1/ga4-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00015 | $0.00548 |
| Opus 5 | $0.00008 | $0.00274 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
ga4-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
/ga4-setup - First-Time Setup
Run the setup script to connect to Google Analytics. Two modes:
- Easy (cloud): dataarsenal.com API key - 50 checks, no local OAuth
- Advanced (local): Google OAuth - 20 checks, everything local
Steps
- Find and run the setup script. Check these locations in order:
- First:
scripts/ga4-setup(CWD is the repo - most common for first run) - Second:
~/.config/data-arsenal/scripts/ga4-setup(already set up, re-running) - Last resort: search for it
- First:
if [ -f scripts/ga4-setup ]; then
python3 scripts/ga4-setup
elif [ -f ~/.config/data-arsenal/scripts/ga4-setup ]; then
python3 ~/.config/data-arsenal/scripts/ga4-setup
else
SCRIPT=$(find ~ -maxdepth 5 -path "*/data-arsenal*/scripts/ga4-setup" -type f 2>/dev/null | head -1)
if [ -n "$SCRIPT" ]; then
python3 "$SCRIPT"
else
echo "ERROR: Cannot find ga4-setup script."
echo "Please cd into the data-arsenal-v1 directory and run: python3 scripts/ga4-setup"
fi
fi
-
If setup succeeds, show the user their properties and suggest next steps:
/ga4-audit <property_id>to run health checks/ga4-brief <property_id>for what-changed analysis/ga4-context <client>to create a business context file
-
If setup fails, help diagnose:
- Python version issues: need 3.8+
- pip install failures: setup auto-creates a venv if needed. If it still fails, manually create:
python3 -m venv ~/.config/data-arsenal/venv && ~/.config/data-arsenal/venv/bin/python3 scripts/ga4-setup - OAuth failures (local mode): check browser access, try again
- API key failures (cloud mode): verify key at dataarsenal.com Settings page
- No properties: verify Google account has GA4 access (local) or GA4 is connected at dataarsenal.com (cloud)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 46 lines · 15 tokens per session scan A f17a07e40b8b
ga4-setup is a command published in the GitHub repository ivanovzlatan2/data-arsenal-v1 (5 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 548 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.