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 skills add Citlyze/citlyze-skills --skill citlyze-visibility-reportgit clone --depth 1 https://github.com/Citlyze/citlyze-skillsWrote 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/citlyze/citlyze-skills/citlyze-visibility-report)<a href="https://agentmods.dev/skills/citlyze/citlyze-skills/citlyze-visibility-report"><img src="https://agentmods.dev/badge/skills/citlyze/citlyze-skills/citlyze-visibility-report/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/citlyze/citlyze-skills/citlyze-visibility-report"><img src="https://agentmods.dev/badge/skills/citlyze/citlyze-skills/citlyze-visibility-report.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.00076 | $0.00746 |
| Opus 5 | $0.00038 | $0.00373 |
| Sonnet 5 | $0.00015 | $0.00149 |
| Haiku 4.5 | $0.00008 | $0.00075 |
Grade A, and why
citlyze-visibility-report 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 11d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citlyze visibility report
Produce an executive-ready report on how a brand shows up in AI search engines, comparing the latest completed measurement window to the previous one.
Prerequisites
The Citlyze MCP server must be connected (setup guide). All Citlyze tools are read-only. When a tool takes measurement_window_id and none is given, it defaults to the latest completed window.
Workflow
- Orient. Call
get_workspace_overview. Note the workspace name, target brand,active_prompts,active_engines,tracked_competitors, andlatest_completed_window. - Pick windows. Call
list_measurement_windowswithstatus: "completed". Take the two most recent windows. If only one exists, report a single-window snapshot and say trend data needs a second window. - Pull metrics for both windows. Call
get_visibility_overviewonce per window. Each row inby_brand_enginecarries:visibility_score,mention_rate,citation_rate,source_rate,avg_prominence,share_of_answer, andn_runs. - Competitive standings. Call
list_competitor_visibilityfor the latest window.by_brandis sorted byvisibility_score; note the target brand's rank and the gap to the leader. - Headline movers. Compute per-engine deltas between the two windows for the target brand. Flag any engine where
visibility_scoremoved notably in either direction. Always sanity-check surprising swings againstn_runs: a big move on very few runs is weak evidence, so say so. - Write the report in this shape:
- TL;DR - three sentences: overall direction, best engine, biggest risk.
- Scoreboard table - one row per engine: previous score, current score, delta, mention rate, citation rate.
- Competitive position - rank, gap to leader, any competitor overtakes since last window.
- Watch items - low-
n_runscaveats, engines with falling citation rate, anything needing a decision.
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.
- 11d ago First seen · 41 lines · 76 tokens per session scan A 40d2825e6618
citlyze-visibility-report is a skill published in the GitHub repository Citlyze/citlyze-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 746 once invoked, about $0.0004 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
ganhuo-geo-engineer
Use this Skill when the user provides an existing article, product page, tutorial, FAQ, or knowledge note and wants to rebuild it into a GEO or AI-search-friendly content asset. Use it for old-content refresh, citation-readiness improvement, answer-first restructuring, GEO upgrades, and Ganhuo AI content workflows. Do…
xerj-code
Reference-coding with XERJ. Clone the libraries that already solved your problem, index them locally, and retrieve the exact implementation before writing code — so the agent reads passages instead of re-deriving algorithms across retry loops. Use when starting a task in an unfamiliar API, porting an algorithm, or…
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
validation-doctor
Check Brave Search and Chrome DevTools MCP availability and provide exact setup snippets. Use when validation dependencies are missing or uncertain.