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/makefile-dev-workflow/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/makefile-dev-workflow)<a href="https://agentmods.dev/skills/raphaelmansuy/edgequake/makefile-dev-workflow"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/makefile-dev-workflow/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/makefile-dev-workflow"><img src="https://agentmods.dev/badge/skills/raphaelmansuy/edgequake/makefile-dev-workflow.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.00048 | $0.02248 |
| Opus 5.5 | $0.00019 | $0.00899 |
| Sonnet 5.5 | $0.00010 | $0.00450 |
| Haiku 4.5 | $0.00005 | $0.00225 |
Grade A, and why
makefile-dev-workflow 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 1mo 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Makefile Development Workflow
When to use
Use this skill when you need to:
- Start development services (database, backend API, frontend)
- Stop services cleanly
- Run end-to-end tests with Playwright
- Check service health status
- Build and deploy applications
- Clean build artifacts
- Manage the full development stack with a single command
Core concepts
The repository includes a unified Makefile (at repo root) that wraps complex shell commands into simple targets. This replaces scattered docker-compose commands and cargo/npm invocations with a consistent interface.
Key directories
edgequake/: Rust backend API (port 8080)edgequake_webui/: Next.js frontend (port 3000)edgequake/docker/: Docker configuration with docker-compose.yml (contains PostgreSQL + pgvector + Apache AGE)
Quick start commands
Start full development stack (all services)
make dev
Starts PostgreSQL, Rust backend, and Next.js frontend in parallel. Displays URLs for all services.
Start full stack with local Langfuse v4
make dev-langfuse # foreground
make dev-bg-langfuse # background (agentic)
make spec124-langfuse-e2e # one-command live Settings + sessions (needs Ollama or OPENAI_API_KEY)
Starts isolated Langfuse (UI http://localhost:3310) plus the EdgeQuake stack, and injects Compose init keys into the backend (overrides Cloud/placeholder keys in .env). make stop does not tear Langfuse down (make langfuse-down).
Stop all services
make stop
Kills all running processes and stops Docker containers gracefully.
Check service status
make status
Shows health of backend, frontend, and database with actual health checks and endpoints.
Service-specific commands
Database management
make db-start # Start PostgreSQL container (port 5432)
make db-stop # Stop PostgreSQL gracefully
make db-logs # View PostgreSQL logs in real-time
make db-shell # Open psql shell into the database
make db-reset # DANGER: Delete all data and reinitialize database
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.
- 1mo ago First seen · 429 lines · 48 tokens per session scan A 4d78c4fc350b
makefile-dev-workflow is a skill published in the GitHub repository raphaelmansuy/edgequake (2,281 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 2,248 once invoked, about $0.0002 per session on Opus 5.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
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…
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.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.