dekko-daemon skillA
dekko-daemon is agent-read markdown (skill) from aahlijia/dekko: Start dekko's background daemon before a session that will run many bare `dekko` CLI commands via Bash (not the MCP tools) against a large or medium repo. Trigger when you're about to run several dekko CLI invocations in a row on the same repo — a long refactor loop, a batch of query/search/outline calls, or a hook/script context — and want to avoid each one reparsing map.json from scratch..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Warming up repeated `dekko` CLI calls with the daemon `dekko daemon start` spawns a small per-repo background process that keeps a warm, in-memory map index across CLI invocations, instead of each one reloading and re-indexing `map.json` from disk. It only matters for the **bare CLI path** (commands run via Bash) — if you're calling the MCP tools (`mcp__dekko__*`) instead, skip this: the MCP server already keeps its own warm per-process cache (`Context.index_cache`) independently, by design, so nothing here applies there. ## When to start it ```sh dekko daemon start # spawns it, returns immediately ``` Worth doing at the start of a Bash-CLI-heavy stretch of work — a refactor loop running `query`/`affected`/`workset` repeatedly, a batch of `outline`/`search` calls while orienting in a large repo, or scripted/hook invocations. Skip it for a one-off `dekko map` or a single query; the daemon adds spin-up overhead that isn't worth it for one call. On a small repo (fast reload already), it's rarely worth the trouble either way. Read-only subcommands route through it transparently once running (`query`, `search`, `workset`, `diff`, `affected`, `outline`, …
Read the whole file at its exact version.
How to install
mdr add aahlijia/dekko/dekko-daemon@git:20260922.4966520mdr add aahlijia/dekko/dekko-daemon@sha256:05117d9412b64d70Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_f63b4m5sour3bn35)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.4966520 latest | 2026-09-22 | 4966520 | 4,110 B | A | view · diff |
| git:20260814.fcff4aa | 2026-08-14 | fcff4aa | 4,079 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4110 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
aahlijia/dekko · 5 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_f63b4m5sour3bn35 GET https://markdownregistry.com/api/v1/resolve?ref=aahlijia/dekko/dekko-daemon GET https://markdownregistry.com/api/v1/blob/05117d9412b64d70a7281fe498e9f32ae9bbf8c7a7ce71c99377781e51abcb87
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.