managed-codebase-context skillA
managed-codebase-context is agent-read markdown (skill) from yeaight7/agent-powerups: Use when connecting to a managed codebase-context MCP/session service, checking stale maps, or safely using MCP-provided repository context..
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
# Managed Codebase Context ## When to use Use when a persistent codebase-context MCP server is available and the task requires broad architectural context, symbol inventory, or cross-file navigation that would be expensive to reconstruct from scratch on each turn. ## Requirements / Checks - Check MCP transport type: stdio (local, one-off) vs HTTP (requires a running server). - Do not run `npx -y` or start server processes without user approval. - Verify server `cwd`, env variables, timeout, and workspace path scope. - Confirm cleanup behavior for spawned stdio processes before starting long-running tasks. ## Workflow 1. **Select transport**: - **stdio**: suitable for local, ephemeral sessions started per task. - **HTTP**: use only when a local server is already confirmed to be running. 2. **Connect with timeout** — set a connection timeout; do not let the agent hang indefinitely if the server never initializes. 3. **Retrieve context** — fetch the current codebase map, symbol index, or architectural summary as available. 4. **Validate freshness** — a map is stale if any of the following are true: …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/managed-codebase-context@git:20260515.e1432a3mdr add yeaight7/agent-powerups/managed-codebase-context@sha256:7da4ed44bad082edPin 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_3rsopyz7uwzjynn2)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260515.e1432a3 latest | 2026-05-15 | e1432a3 | 2,952 B | A | view · diff |
| git:20260505.2286586 | 2026-05-05 | 2286586 | 1,798 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 (2952 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_3rsopyz7uwzjynn2 GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/managed-codebase-context GET https://markdownregistry.com/api/v1/blob/7da4ed44bad082ed160a11490d792d79e5451504581ec0d8a051905bcc8a7b24
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