dekko-notes skillA
dekko-notes is agent-read markdown (skill) from aahlijia/dekko: Read and write dekko's symbol-anchored notes in any repo with a .dekko/ directory. Trigger every time you pull a symbol's context (query_symbol, get_context_pack, dekko query/context), right after a non-obvious change, and right after any rename/move/signature edit (to sweep orphaned notes). Notes are durable, committed annotations keyed by symbol id — they carry rationale grep/Read cannot show..
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
# Keeping dekko notes current dekko stores **symbol-anchored notes** in `.dekko/notes.json`, keyed by symbol id (`path::Qualified.name`). They are committed to git and shown inline by `query_symbol` / `get_context_pack` (CLI: `dekko query symbol` / `dekko context`). See the `dekko-orient` skill for target syntax (bare name, `Class.method`, `file.py:name`, or the tolerated `::` form) and for when to reach for dekko over grep/Read generally. ## Consult notes before editing Whenever you pull a symbol's context, read any `note:` lines first — they record rationale, gotchas, and constraints the code alone does not show. Treat a note as settled context: don't re-derive what it already tells you by reading the code again. Call the `list_notes` MCP tool (or `dekko note list <sym>`) directly if you need to see a symbol's notes outside a context pack, or `dekko note list` with no target to see every note in the repo before a large change. If a note turns out to be wrong or obsolete, fix it (`note rm` then `note add`) rather than leaving it to mislead the next reader. ## Write a note after a non-obvious change After a change whose reasoning is not evident from the diff — a …
Read the whole file at its exact version.
How to install
mdr add aahlijia/dekko/dekko-notes@git:20260922.4966520mdr add aahlijia/dekko/dekko-notes@sha256:8dd8e793315dac84Pin 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_hfwmgii7qfnqr4u6)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.4966520 latest | 2026-09-22 | 4966520 | 3,020 B | A | view · diff |
| git:20260803.ca49afc | 2026-08-03 | ca49afc | 2,470 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 (3020 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_hfwmgii7qfnqr4u6 GET https://markdownregistry.com/api/v1/resolve?ref=aahlijia/dekko/dekko-notes GET https://markdownregistry.com/api/v1/blob/8dd8e793315dac8400cde787586572753c6882ba1a7c6a66e97e0fe3c0ee2711
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.