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-map-page-by-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-map-page-by-page)<a href="https://agentmods.dev/skills/raphaelmansuy/edgequake/ux-ui-map-page-by-page"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/ux-ui-map-page-by-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-map-page-by-page"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/ux-ui-map-page-by-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00680 |
| Opus 5 | $0.00032 | $0.00340 |
| Sonnet 5 | $0.00013 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
ux-ui-map-page-by-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 13d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX/UI Map (Page-by-Page)
When to use
Use this skill when the user asks to:
- capture screens page by page
- avoid “capture everything then analyze later”
- generate/update
ux_ui_map/artifacts
Key rule (memory-safe)
Process exactly one route at a time:
- Navigate route
- Capture screenshots (desktop/tablet/mobile)
- Immediately write/update the page doc in
ux_ui_map/pages/ - Immediately write/update the page request in
ux_ui_map/requests/ - Only then move to the next route
Do not keep previous pages in working context.
Output contract
Write these files as you go:
ux_ui_map/pages/{page}.md(page documentation)ux_ui_map/screenshots/{page}/...png(screenshots)ux_ui_map/requests/{page}.json(analysis request inputs)ux_ui_map/capture-index.jsonl(append-only log, one JSON object per captured route)
Templates:
- Page doc template: assets/page-template.md
- Request JSON template: assets/request-template.json
Helper script:
- Scaffold/validate per-page artifacts: scripts/page_artifacts.mjs
Script usage
Scaffold the expected files/folders for one page:
node .github/skills/ux-ui-map-page-by-page/scripts/page_artifacts.mjs scaffold --page dashboard --route /
Validate that a page has its 3 required screenshots and docs:
node .github/skills/ux-ui-map-page-by-page/scripts/page_artifacts.mjs validate --page dashboard
Naming
{page}is a stable slug (e.g.dashboard,documents,query,graph,settings,api-explorer,login).- Screenshot names include viewport suffix:
desktop.png,tablet.png,mobile.png.
Minimal checklist per route
- Route loads without hard failure (HTTP/blank page)
- 3 screenshots saved (desktop/tablet/mobile)
-
ux_ui_map/pages/{page}.mdcreated/updated -
ux_ui_map/requests/{page}.jsoncreated/updated - Capture appended to
ux_ui_map/capture-index.jsonl
Example prompts that should trigger this skill
- “Capture the UI page-by-page and write analysis immediately.”
- “Update the UX/UI mapping, but don’t blow the context window.”
- “Generate
ux_ui_map/artifacts for all routes.”
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 68 lines · 63 tokens per session scan A c43c25b1bc5f
ux-ui-map-page-by-page is a skill published in the GitHub repository raphaelmansuy/edgequake (2,092 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 680 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.