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/navraj007in/architecture-cowork-pluginWrote 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/navraj007in/architecture-cowork-plugin/analytics-setup)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/analytics-setup"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/analytics-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/navraj007in/architecture-cowork-plugin/analytics-setup"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/analytics-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.00021 | $0.00665 |
| Opus 5 | $0.00010 | $0.00332 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
analytics-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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:analytics-setup
Trigger
/architect:analytics-setup [options]
Options:
[provider:ga4|posthog|mixpanel|amplitude|plausible]— override provider (default: GA4)[non_interactive:true]— skip questions, use defaults
Purpose
Product insights drive decisions. This command wires analytics infrastructure: GA4, PostHog, Mixpanel, Amplitude, or Plausible SDKs with typed event tracking, GDPR-compliant consent management, and privacy-by-default settings. Generates src/lib/analytics.ts with event tracking utilities and consent hooks.
Workflow
Quick Navigation
| Phase | Steps |
|---|---|
| Setup | Step 1 |
| Configuration | Step 2 |
| Generation | Step 3 |
| Completion | Step 4 · Step 5 |
Step 1: Read Context
ℹ️ CONTEXT LOADING: _state.json → SDL
Read:
_state.json.design.personality(product stage)_state.json.personas[](regions → GDPR requirement)- Tech stack (frontend framework)
Step 2: Ask Configuration
❓ DECISION POINT: Analytics provider and consent approach
If not non_interactive:
- Which provider? GA4, PostHog, Mixpanel, Amplitude, Plausible
- GDPR consent required? (auto-detect from EU regions in personas)
Step 3: Generate Analytics Files
Create:
src/lib/analytics.ts— Typed event tracking (TypeScript)src/hooks/useConsent.ts— Consent management hook.env.example— API key placeholderssrc/components/ConsentBanner.tsx— GDPR consent UI
Example events tracked:
- Page views
- Outbound clicks
- Form submissions
- Error events
- Custom business events (signup, purchase, etc.)
Step 4: Log Activity
{"ts":"<ISO-8601>","phase":"analytics-setup","outcome":"completed","provider":"ga4","gdpr_enabled":true,"files_generated":4,"summary":"Analytics configured: GA4 with typed tracking, GDPR consent banner, consent hook."}
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 · 88 lines · 21 tokens per session scan A bd7ac0776b3e
analytics-setup is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 665 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
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
nyann:apply
Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…
nyann:hotfix
Create the branch topology for a patch release against a previously tagged version. Ensures release/ . exists from the source tag, then creates hotfix/ off it. After this, the user commits the fix and runs /nyann:release from the hotfix branch.
nyann:ship
Open a GitHub pull request AND merge it in one step. Default uses GitHub's native auto-merge (returns immediately with outcome:"queued"); --client-side polls for green CI in the foreground then runs gh pr merge. Requires gh installed + authed.
nyann:cleanup-branches
Prune local branches whose work is already merged into the base. Lists candidates first, then applies on --yes. Mirrors the safe-delete semantics of git branch -d (lowercase d): nothing unmerged is touched.
nyann:fleet
Manage the fleet registry of local repos and show the cross-repo health dashboard — per-repo score, trend sparkline, drift counts, worst category, sorted worst-first. Read-only: it audits and reports, never remediates (that's /nyann:fleet-retrofit).