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-brief)<a href="https://agentmods.dev/commands/ivanovzlatan2/data-arsenal-v1/ga4-brief"><img src="https://agentmods.dev/badge/commands/ivanovzlatan2/data-arsenal-v1/ga4-brief/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-brief"><img src="https://agentmods.dev/badge/commands/ivanovzlatan2/data-arsenal-v1/ga4-brief.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.00014 | $0.06424 |
| Opus 5 | $0.00007 | $0.03212 |
| Sonnet 5 | $0.00003 | $0.01285 |
| Haiku 4.5 | $0.00001 | $0.00642 |
Grade A, and why
ga4-brief 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 582 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ga4-brief - Structured What-Changed Analysis
Four-phase analysis: SCAN → DETECT → INVESTIGATE → REVIEW → DEDUPLICATE → OUTPUT. Includes quality gate to filter noise and a deduplication check against previous briefings.
Usage
/ga4-brief <property> [--days 7]
<property> can be: numeric property ID, project slug, client name, or URL. See Property Resolution below.
Steps
Step 0: Setup
Language check: Read ~/.config/data-arsenal/config.json.
- If
languageis set → use that language in its native script for all commentary and recommendations. Bulgarian = Cyrillic (кирилица), NOT Latin transliteration. Data labels and GA4 metric names stay in English. - If
languageis NOT set (first run) → output as plain text (NOT AskUserQuestion): "What language should I use? (English / Bulgarian / other)" Wait for user response, interpret it, save to config.json so it's never asked again.
Property resolution: Resolve <property> to a numeric property_id:
- If numeric → use as property_id directly
- If matches a project slug in
~/.config/data-arsenal/projects/→ read property_id from that project's config.json - If neither → run
resolve_property()from_ga4_lib.pyto search GA4 account by name - If still not found → ask user to clarify
Auto-load project: Scan ~/.config/data-arsenal/projects/*/config.json for a project where property_id matches. If found:
- Load
config.json(business context) - Load
context.md(narrative context) - Load
data-quality.jsonif exists (audit caveats) - Load
briefing-log.jsonif exists (previous findings for dedup)
If no context found, warn that analysis will be generic and suggest /ga4-context first.
Step 1: SCAN — Run reports
a. Run what-changed reports:
Find the script in order:
~/.config/data-arsenal/scripts/ga4-what-changed(post-setup, primary)scripts/ga4-what-changed(CWD is the repo)- If neither exists, tell the user to run
/ga4-setupfirst
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.
- 11d ago First seen · 582 lines · 14 tokens per session scan A 44f8380f3e23
ga4-brief is a command published in the GitHub repository ivanovzlatan2/data-arsenal-v1 (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 6,424 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.