Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add shalintripathi/organic-os/plugin install 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/skills/shalintripathi/organic-os/onsite-measure)<a href="https://agentmods.dev/skills/shalintripathi/organic-os/onsite-measure"><img src="https://agentmods.dev/badge/skills/shalintripathi/organic-os/onsite-measure/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/skills/shalintripathi/organic-os/onsite-measure"><img src="https://agentmods.dev/badge/skills/shalintripathi/organic-os/onsite-measure.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.00040 | $0.00474 |
| Opus 5 | $0.00020 | $0.00237 |
| Sonnet 5 | $0.00008 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
onsite-measure 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 12d 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
Measure outcomes (closing the loop)
- Scan outcomes/ for records with a due measurement date <= today that lack that measurement.
- Per record: pull GSC for the target URL - clicks/impressions/CTR/position for the 7 (or 28) days after the change vs the same window before. GSC data lags 2-3 days: fetch the day-7 window no earlier than day 10, and the day-28 window no earlier than day 31. No GSC connector: record "unmeasured (no GSC)" honestly.
- Append the delta to the outcome record + one signal line
("outcome : position 8.2 -> 5.9 after title rewrite").
"After" is a sequence, not a cause. Attributing the move to the change
follows the attribution rule (canonical in hoo-daily's anomaly
section, step 2.7): the claim, the comparison actually run, and what
would falsify it - for example "compared the 28 days after against the
same 28-day window before, same URL; if the site-wide trend moved the
same way over those windows, the change is not what did it." Where
that comparison was not run, the record reads
cause: unknown (before/after window not compared)and keeps the delta. A measured number with an honest unknown is what lets the reflector score a skillbook entry later; a confident story that nobody checked teaches the loop the wrong lesson. - Wins and losses BOTH matter: the reflector reads outcomes to score
skillbook entries helpful/harmful. At day-28, set the item to measured
via
PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -m core status <item-path> measured --actor agent. Never edit brain frontmatter directly. The contract CLI is the only write path for status and approvals.
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.
- 12d ago First seen · 34 lines · 40 tokens per session scan A 71911de7aa65
onsite-measure is a skill published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 474 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 skills, from other repositories
seo-vertical-detect
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.
seo-fix-apply
Writer protocol preloaded into the seo-fixer-writer agent — how confirmed SEO/AI-search fixes are applied (git pre-flight, backup, Edit/Write for local diffs, ticketed adapter CLIs for remote targets, re-verify, publish only on a second ticket, rollback) and the findings-array output contract. Used only by the fix…
audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured…
ai-visibility
Fast-path AI visibility — get a brand's 0–100 Akii Visibility Score (computed by an open-source LLM judge against the brand's public footprint) with four-dimension breakdown AND a per-engine proxy map for ChatGPT, Claude, Gemini, Perplexity, Copilot, and Google AI Overviews based on FirstPageSage signal weights.…
seo-audit
Single audit entry point — surface-level scorecard or deep infrastructure dive depending on the requested mode. Default full mode produces a multi-layer scorecard across all 9 areas (crawlability, indexation, meta tags, headings, images, Core Web Vitals, JS rendering, mobile + security, structured data, internal…
optimize-page
Comprehensive single-page optimization across all three layers — traditional SEO (title / meta / H1 / internal links), AEO (chunk quality, direct-answer leads, FAQ extraction), and GEO rewrites using the tactics published by the Princeton/IIT Delhi GEO study (citation integration, expert quotes, statistics enrichment…