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/e2e-test-service-management/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/e2e-test-service-management)<a href="https://agentmods.dev/skills/raphaelmansuy/edgequake/e2e-test-service-management"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/e2e-test-service-management/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/e2e-test-service-management"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/e2e-test-service-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 Tool Misuse · line 446 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- high Privilege Escalation · line 513 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 402 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00046 | $0.04061 |
| Opus 5 | $0.00023 | $0.02031 |
| Sonnet 5 | $0.00009 | $0.00812 |
| Haiku 4.5 | $0.00005 | $0.00406 |
Grade C, and why
e2e-test-service-management scanned grade C with 2 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| Frontend build errors | Clear cache: `cd edgequake_webui && rm -rf .next node_modules && make frontend-dev` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Requires make, cargo, Node.js/pnpm, Docker Desktop with docker-compose support, and curl for health checks. How it starts
The opening of the file, as written. The whole thing — 738 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Service Management
When to Use This Skill
Use this skill when you need to:
- Start all services for interactive E2E testing
- Verify service health before running tests
- Monitor logs during test execution
- Stop services cleanly after testing
- Debug test failures with real backend/database
- Test with different configurations (mock LLM vs real LLM)
- Manage service lifecycle in CI/CD pipelines
Perfect For
✅ E2E Testing Workflows - Running Playwright tests with real services
✅ Interactive Debugging - Testing features manually with live backend
✅ Service Isolation - Starting only specific services
✅ Health Monitoring - Detecting service crashes/failures
✅ Log Inspection - Troubleshooting backend/database issues
✅ Test Isolation - Cleaning services between test runs
Service Architecture
Services Overview
┌─────────────────────────────────────────────┐
│ E2E Testing Environment │
├─────────────────────────────────────────────┤
│ │
│ Frontend (Next.js) Port 3000 │
│ ├─ Playwright Tests │
│ ├─ Hot Reload Development │
│ └─ TypeScript/React Components │
│ │
│ Backend (Rust) Port 8080 │
│ ├─ RAG Query Engine │
│ ├─ Document Processing │
│ ├─ Knowledge Graph API │
│ └─ LLM Integration │
│ │
│ Database (PostgreSQL) Port 5432 │
│ ├─ pgvector Extension (embeddings) │
│ ├─ Apache AGE (graph storage) │
│ ├─ Conversation History │
│ └─ Document Metadata │
│ │
└─────────────────────────────────────────────┘
Service Dependencies
What ships with it
2 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.
- 9d ago First seen · 738 lines · 46 tokens per session scan C b932d86f999b
e2e-test-service-management is a skill published in the GitHub repository raphaelmansuy/edgequake (2,089 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 4,061 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
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…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
html-preview
A guidance skill for adding small, static HTML/CSS visual previews to Markdown when a diagram, comparison, timeline, metric display, or layout sketch would be clearer than text. It does not use JavaScript.
potpie-repo-baseline
Use when establishing, refreshing, or deeply understanding a repository's baseline memory in Potpie: purpose, application type, features, services/modules, environments, deploy shape, dependencies, API contracts, datastores, integrations, ownership, and explicit preferences. The harness reads authored and…
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.