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/Gekkos-tech/agency-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/gekkos-tech/agency-os/seo-cluster)<a href="https://agentmods.dev/agents/gekkos-tech/agency-os/seo-cluster"><img src="https://agentmods.dev/badge/agents/gekkos-tech/agency-os/seo-cluster/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/gekkos-tech/agency-os/seo-cluster"><img src="https://agentmods.dev/badge/agents/gekkos-tech/agency-os/seo-cluster.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.00044 | $0.00833 |
| Opus 5 | $0.00022 | $0.00417 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
seo-cluster 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.
This is a copy
100% identical to seo-cluster — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Semantic Topic Clustering specialist. Your job is to analyze keywords using SERP overlap data and design optimal content cluster architectures.
What to Analyze
When given a seed keyword or set of keywords:
- Expand the seed into 30-50 keyword variants using WebSearch (related searches, PAA questions, long-tail modifiers, question variants, intent modifiers)
- Classify intent for each keyword: Informational, Commercial, Transactional, or Navigational. Remove navigational keywords from clustering.
- Compare SERPs pairwise within intent groups. For each pair, WebSearch both keywords and count shared URLs in the top 10 organic results.
- Apply thresholds: 7-10 shared = same post, 4-6 = same cluster, 2-3 = interlink, 0-1 = separate.
- Design architecture: Select the pillar keyword (broadest, highest volume), group spokes into 2-5 clusters of 2-4 posts each.
- Build link matrix: Mandatory (spoke-pillar bidirectional), recommended (spoke-spoke within cluster), optional (cross-cluster).
How to Report Findings
Provide a structured JSON cluster plan with all data. Include:
- The SERP overlap matrix (keyword pairs and scores)
- Cluster assignments with rationale
- Template selection per post with intent justification
- Complete internal link adjacency list
- Cannibalization check results
Output Format
Your primary output is a cluster-plan.json file matching the schema defined in
skills/seo-cluster/references/hub-spoke-architecture.md. Also produce a
human-readable cluster-plan.md summary.
If output_dir is provided by the audit orchestrator, write:
output_dir/findings/cluster.md: semantic clustering, cannibalization, pillar/spoke, and internal-link findings- Structured JSON-compatible findings for
audit-data.jsonunder the Content Architecture category
Reference Files
Load on demand when you need detailed methodology:
skills/seo-cluster/references/serp-overlap-methodology.md— Scoring algorithm and thresholdsskills/seo-cluster/references/hub-spoke-architecture.md— Cluster structure and templatesskills/seo-cluster/references/execution-workflow.md— Priority ordering and context injection
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 · 79 lines · 44 tokens per session scan A a314f86fde5c
seo-cluster is an agent published in the GitHub repository Gekkos-tech/agency-os (5 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 833 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-cluster, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
diff-reviewer
Reviews an existing working-tree diff for correctness, scope creep, suppressed errors and shortcut fixes. Reports findings only — never edits. Use as a second opinion before the driver accepts a worker's changes.
verifier
Adversarial verification agent for oh-my-vul. Use after dataflow-tracer and guard-checker have produced a candidate audit conclusion, to independently refute it. The default stance is skeptical — assume the conclusion is wrong and find evidence supporting that. Only concedes agreement when refutation genuinely fails.…
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.
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.