Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yeaight7/agent-powerups --skill managed-codebase-contextgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/managed-codebase-context)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/managed-codebase-context"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/managed-codebase-context/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/yeaight7/agent-powerups/managed-codebase-context"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/managed-codebase-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00031 | $0.00610 |
| Opus 5.5 | $0.00012 | $0.00244 |
| Sonnet 5.5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
managed-codebase-context 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 -yor 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
-
Select transport:
- stdio: suitable for local, ephemeral sessions started per task.
- HTTP: use only when a local server is already confirmed to be running.
-
Connect with timeout — set a connection timeout; do not let the agent hang indefinitely if the server never initializes.
-
Retrieve context — fetch the current codebase map, symbol index, or architectural summary as available.
-
Validate freshness — a map is stale if any of the following are true:
- Map timestamp predates the last
git committhat touched relevant files. - Map references files that no longer exist.
- Map is missing files present in the current workspace.
- The user reports recent significant refactoring.
- Map timestamp predates the last
-
Refresh when stale — trigger a context refresh only when the map is demonstrably stale. Do not refresh on every request — refreshes are expensive.
-
Use context, then close — read what you need, then close the session. Ensure the client and transport close cleanly. If the server was spawned as a stdio process, kill the process tree if it does not exit within a few seconds.
Staleness Signals
| Signal | Check |
|---|---|
| Map timestamp | Compare to git log --format="%ci" -1 for recently changed files |
| Missing files | Cross-reference map file list with git ls-files |
| Stale symbols | Check if key function/class names in the map exist in current source |
| User-reported | Accept the user's word; trigger refresh without verification |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 59 lines · 31 tokens per session scan A 7da4ed44bad0
managed-codebase-context is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 31 tokens to every session and 610 once invoked, about $0.0001 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-31.
Other skills, from other repositories
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
openlore
Query and publish to an OpenLore knowledge repository over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.
search-shared-sessions
Search an Agent Relay workspace's shared coding-agent sessions for prior work, decisions, fixes, or the context behind a task or pull request. Use when team history could answer the user's question or prevent repeating an investigation.
kb-research
Structured approach to finding and synthesizing information from the user's knowledge base.
narco-check
Memory integrity audit. Detects hallucinations, circular confirmations, and state poisoning. Runs automatically after 2 consecutive failures or at nightly deep dive. Uses Opus 4.6 as the auditor model.