context-docs skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
context-docs is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a subsystem needs persistent context for future agents or engineers -- its boundaries keep being rediscovered the hard way, invariants keep getting violated, or sessions repeatedly ask the same questions about it..
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
## Purpose Large centralized documentation files consume too much context window. Decentralized, module-specific context docs provide targeted information exactly when an agent needs it. ## When to Use - A module's boundaries or invariants keep being rediscovered the hard way - Onboarding or agent sessions repeatedly ask the same questions about a subsystem - After a refactor changed how a module communicates with the rest of the app ## Inputs - The subsystem directory and its public interface - Existing docs, to avoid duplicating the central README or architecture docs ## Workflow 1. **Decide where the context belongs.** Module-specific knowledge goes in a context file *inside* the subsystem directory (e.g., `src/auth/CONTEXT.md`); repo-wide knowledge belongs in the central README or architecture docs — one home per fact, never both: ```bash find src -iname "CONTEXT.md" -o -iname "README.md" # existing context docs rg -ln "<module name>" docs/ # already documented centrally? ``` …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/context-docs@git:20260606.91a5254mdr add yeaight7/agent-powerups/context-docs@sha256:13836e9129c44234Pin 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_wpmvgdidlloeoiy3)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.91a5254 latest | 2026-06-06 | 91a5254 | 2,957 B | A | view · diff |
| git:20260602.e5c71e3 | 2026-06-02 | e5c71e3 | 696 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 (2957 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wpmvgdidlloeoiy3 GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/context-docs GET https://markdownregistry.com/api/v1/blob/13836e9129c442341d4c4c43cfb3bd8cac92e1ed7b8c08f85a669225cb046372
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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups