EdgeQuake is a Rust framework that turns documents into knowledge graphs for GraphRAG, a retrieval-and-generation approach that uses linked facts to help language models find relevant information. It is used to build applications that search and generate answers from document collections.
Borrowing it
Nothing to install: this file belongs to raphaelmansuy/edgequake. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/raphaelmansuy/edgequake/edgequake-main/.github/skills/ux-ui-analyze-single-page/SKILL.mdgit clone --depth 1 https://github.com/raphaelmansuy/edgequakeWrote 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/raphaelmansuy/edgequake/ux-ui-analyze-single-page)<a href="https://agentmods.dev/skills/raphaelmansuy/edgequake/ux-ui-analyze-single-page"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/ux-ui-analyze-single-page/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/raphaelmansuy/edgequake/ux-ui-analyze-single-page"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/ux-ui-analyze-single-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 29 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00058 | $0.00438 |
| Opus 5 | $0.00029 | $0.00219 |
| Sonnet 5 | $0.00012 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
ux-ui-analyze-single-page 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.
What it actually says
Single-Page UI Analysis (Write Immediately)
When to use
Use this skill when:
- screenshots already exist and need describing
- the user wants analysis written out immediately after each page capture
- you must avoid carrying multi-page context
Inputs
ux_ui_map/requests/{page}.jsonux_ui_map/screenshots/{page}/desktop.pngux_ui_map/screenshots/{page}/tablet.pngux_ui_map/screenshots/{page}/mobile.png
Output
ux_ui_map/pages/{page}.md(created/updated immediately)
Rules
- Descriptive only: do not judge, do not recommend, do not assign severity.
- Focus on the hierarchy: page → regions → containers → components → elements.
- If information is uncertain from the screenshot, say so plainly (e.g., “Text is not legible at this resolution”).
- Do not reference previous pages unless explicitly asked.
Procedure
- Load the request JSON to confirm route and expected screenshot paths.
- Inspect desktop screenshot first (structure), then tablet/mobile (responsive changes).
- Write/update the page doc using the template at
ux_ui_map/pages/{page}.md:- Overview (route/title)
- ASCII layout diagram (approximate)
- Screenshot table
- Regions/containers/components
- Stop after writing this one page.
Example prompt that should trigger this skill
- “Analyze the dashboard screenshots and write the page doc now.”
- “Rewrite the corresponding analysis immediately for /documents.”
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 · 47 lines · 58 tokens per session scan A 7f33c9e17361
ux-ui-analyze-single-page is a skill published in the GitHub repository raphaelmansuy/edgequake (2,091 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 438 once invoked, about $0.0003 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-30.
Other skills, from other repositories
rag-remember
Store a fact, decision, or observation into the personal LightRAG knowledge graph immediately.
rag-sync
End-of-session review and sync of learnings to the personal LightRAG knowledge graph.
langchain
Framework for building LLM-powered applications with agents, chains, and RAG. Supports multiple providers (OpenAI, Anthropic, Google), 500+ integrations, ReAct agents, tool calling, memory management, and vector store retrieval. Use for building chatbots, question-answering systems, autonomous agents, or RAG…
graphify
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community…
browserwing-executor
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.
ask-user-question
Ask users questions via the UI. Use when you need clarification, user preferences, or confirmation before proceeding. The user CANNOT see CLI output - this tool is the ONLY way to communicate with them.