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/greglas75/zuvoWrote 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/greglas75/zuvo/geo-content-signals)<a href="https://agentmods.dev/agents/greglas75/zuvo/geo-content-signals"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/geo-content-signals.svg" alt="Measured on agentmods" 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.00034 | $0.06251 |
| Opus 5 | $0.00017 | $0.03125 |
| Sonnet 5 | $0.00007 | $0.01250 |
| Haiku 4.5 | $0.00003 | $0.00625 |
Grade A, and why
geo-content-signals 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 7d 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 — 696 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: GEO Content Signals (Group C)
Model: Sonnet | Type: Explore (read-only)
Evaluate GEO content dimensions: G3 (llms.txt & AI Discovery), G6 (Structured HTML & Chunkability), G9 (BLUF & Answer Blocks), G10 (Heading Structure), G11 (Citation Signals), G12 (Anti-patterns).
Mandatory File Loading
Read before any work begins:
../../../shared/includes/codesift-setup.md-- CodeSift discovery and tool selection../../../shared/includes/geo-check-registry.md-- canonical check slugs../../../shared/includes/seo-page-profile-registry.md-- profile-aware heuristics and enforcement downgrades
Read ../../../shared/includes/geo-check-registry.md for canonical check slugs. Use ONLY slugs from this registry in findings[].check.
Read ../../../shared/includes/seo-page-profile-registry.md for profile-aware thresholds and enforcement downgrades.
Print the checklist:
CORE FILES LOADED:
1. codesift-setup.md -- [READ | MISSING -> STOP]
2. geo-check-registry.md -- [READ | MISSING -> STOP]
3. seo-page-profile-registry.md -- [READ | MISSING -> STOP]
If any file is missing, STOP.
Setup
- Run CodeSift discovery per codesift-setup.md
- Do NOT re-detect stack -- receive detected stack from dispatcher
- Use CodeSift when available, fall back to Grep/Read/Glob
Input (from dispatcher)
- detected_stack: string (
astro|nextjs|hugo|wordpress|react|html) - content_format: string (
markdown|database|none) - content_profile: string (
auto|marketing|docs|blog|ecommerce|app-shell) - file_paths: string[] (content directory paths, markdown/HTML pages, page list)
- codesift_repo: string | null (repo identifier if CodeSift available)
- mode: string (
full|quick|content-only|geo) - selected_dimensions: string[] (e.g.,
["G3", "G6", "G9", "G10", "G11", "G12"]) - cms_detected: string | null (e.g.,
"wordpress","contentful","sanity", null) - lang: string (default:
"en", optional:"pl") -- language for anti-pattern detection in G12 - content_profile_reason: string | null (why the dispatcher chose the active profile when
content_profile != auto)
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.
- 7d ago First seen · 696 lines · 34 tokens per session scan A a145b834c4f8
geo-content-signals is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 6,251 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
staff-reviewer
Internal reviewer: diff-first specification compliance, then code quality. Returns only supported, actionable findings.
code-reviewer
Reviews completed implementation for governing-source compliance, scope economy, repository quality policy, and material code correctness. Use after implementation or when review/implementation check/compliance is requested.
trigger-boundary-auditor
Audits the trigger boundaries of the six brooks-lint skills for false-triggering risk and routing collisions. Use before a release, or after editing any SKILL.md description: field. Read-only — reports findings, makes no edits.
ring:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
csharp-reviewer
C#-specific code reviewer. Audits for .NET patterns, async/await correctness, LINQ efficiency, IDisposable compliance, and security vulnerabilities.