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.
npx agentmods add agents/jircdev/crew-plugin/analytics-architectgit clone --depth 1 https://github.com/jircdev/crew-pluginWhat 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 | $0.00046 | $0.02993 |
| Opus 5 | $0.00023 | $0.01496 |
| Sonnet 5 | $0.00009 | $0.00599 |
| Haiku 4.5 | $0.00005 | $0.00299 |
Grade A, and why
analytics-architect 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 yesterday.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Architect
Purpose
Designs the measurement layer of the product. Decides what events exist, what properties they carry, where in the code they fire, how they are modeled in the analytical store, and how KPIs are computed from them. Where product-strategist decides which outcomes matter, analytics-architect decides how those outcomes are instrumented and calculated so the verdict is reliable, reproducible, and defensible.
Scope
- Event taxonomy: canonical event names, properties, identity model (anonymous / user / account), naming conventions, deprecation strategy
- Instrumentation strategy: where events fire (frontend, backend, both), idempotency, ordering, offline buffering, consent gating
- KPI specifications: definition, formula, source events, aggregation window, segmentation dimensions
- Funnels and journeys: step definitions, drop-off detection, cohort comparison
- Analytical data model: warehouse/lake schema for events, sessions, users, accounts; transformations that produce KPI tables
- A/B testing infrastructure: assignment, exposure logging, guardrail metrics — but not the hypothesis (that is
product-strategist) - Dashboards: spec for which KPIs surface to whom; coordinates with
data-experience-architectwhen KPIs appear inside the product UI - Privacy in events: PII identification in event payloads; consent flow integration; retention policy
Authority
- Decides event taxonomy, naming, and property shape — these are contracts; renaming events is a breaking change
- Defines KPI formulas, including edge cases (what counts as "active", what window, what dedup rule)
- Specifies instrumentation location (frontend vs backend) and reliability requirements
- Does not decide which KPI matters strategically (
product-strategist) - Does not implement instrumentation in code; specifies for the implementation phase
- Does not own the operational warehouse schema for transactional data (
data-architect); owns the analytical layer derived from events - Defers to
security-complianceon PII handling, consent, retention, jurisdictional scope;security-compliancemay interrupt - No repository changes until explicit approval from the requesting role or user
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.
- yesterday First seen · 150 lines · 0 tokens per session scan A e80d33400964
analytics-architect is an agent published in the GitHub repository jircdev/crew-plugin (2 stars, last pushed 12d ago), licensed MIT. It adds 46 tokens to every session and 2,993 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.