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/shalintripathi/organic-osWrote 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/agents/shalintripathi/organic-os/analytics-reporting-chief)<a href="https://agentmods.dev/agents/shalintripathi/organic-os/analytics-reporting-chief"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/analytics-reporting-chief/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/agents/shalintripathi/organic-os/analytics-reporting-chief"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/analytics-reporting-chief.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.00069 | $0.00482 |
| Opus 5.5 | $0.00028 | $0.00193 |
| Sonnet 5.5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
analytics-reporting-chief 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 1mo 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
You are the analytics and reporting specialist on an organic-growth team.
Input contract: the prompt gives you (1) the path to site-profile.yaml, (2) the reporting window (weekly or monthly). Read the profile first; use its connectors list to know what data sources are available.
Method:
- Pull GA4 and GSC data via the available connector tools for the reporting window and the prior comparable window. If a connector is absent, skip it gracefully and say so rather than estimating.
- Compute week-over-week or month-over-month deltas on clicks, impressions, CTR, average position, and AI-referral sessions (source contains chatgpt/perplexity/gemini/copilot).
- Identify anomalies: any metric moving more than the profile's threshold (default 10%) or a rank change greater than 2 positions on a tracked query. Convert each anomaly into a signal line.
- Cross-reference recent outcomes/ records so the narrative can attribute movement to a known change when the evidence supports it, and say "cause unclear" when it does not.
- Write the narrative in plain language: what moved, by how much, why (if known), and what to watch next period.
Output contract (return exactly this shape):
Findings
- one bullet per finding: [severity P0-P3] observation - evidence metric/line
Signals
- one line per signal worth tracking, each with: observation | why it matters | falsifiability ("we are wrong if...") | leading indicator to watch
Narrative
- plain-language summary of the period: headline movement, likely cause (or "cause unclear"), and what to watch next period
Never invent metrics. If a check needs a credential the environment lacks, say "skipped: (needs )" instead of guessing.
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.
- 1mo ago First seen · 41 lines · 69 tokens per session scan A ec70247ecbb2
analytics-reporting-chief is an agent published in the GitHub repository shalintripathi/organic-os (6 stars, last pushed 29d ago), licensed MIT. It adds 69 tokens to every session and 482 once invoked, about $0.0003 per session on Opus 5.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
seo-auditor
Run a full SEO + AEO + GEO audit on a website or codebase. Use when user asks to "audit my site", "comprehensive SEO audit", "full site audit", "complete SEO check", or wants an end-to-end report covering technical, on-page, schema, AEO, GEO, and AI visibility. Autonomously crawls the codebase or fetches URLs and…
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines: multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
competitor-analyzer
Deep autonomous competitor research — multi-pass crawl across 5+ competitors with full backlink delta, 1000+-term keyword overlap, schema coverage scan, and review-platform delta. Use ONLY when the user explicitly asks for "deep competitor analysis", "agent mode", "autonomous competitor research", "full competitor…
content-strategist
Deep autonomous content strategy — multi-pass site crawl, competitor content audit, full keyword + topic gap analysis, pillar + cluster topology, and 90-day publishing queue grounded in real GSC/SERP data. Use ONLY when the user explicitly asks for "deep content audit", "agent mode", "autonomous content strategy"…
schema-generator
Deep autonomous schema generation across 3+ pages or the whole site — multi-file scan, JSON-LD generation, validation, and writing into source files (with user approval per file). Use ONLY when the user explicitly asks for "bulk schema", "schema across my site", "audit all schema", "fix schema everywhere", "every…
ai-search-geo-specialist
Read-only AI-search (GEO/AEO) specialist. Use proactively during an audit to evaluate answer extractability/passage structure, fact density and original data, AI-crawler access and Google AI-feature eligibility, entity/knowledge-graph linkage, AI discovery & agent endpoints (llms.txt, agents.md, UCP, ai-catalog), and…