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 context-docsgit 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/context-docs)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/context-docs"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/context-docs/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/context-docs"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/context-docs.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.00043 | $0.00640 |
| Opus 5.5 | $0.00017 | $0.00256 |
| Sonnet 5.5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
context-docs 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
-
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:find src -iname "CONTEXT.md" -o -iname "README.md" # existing context docs rg -ln "<module name>" docs/ # already documented centrally? -
Document only the boundaries. How does this module communicate with the rest of the app? What are its critical invariants? Not implementation detail the code already states.
-
Keep it terse. Bullet points and exact file paths. No transient notes — session state, TODO lists, and progress logs belong in handoff documents, not context docs.
-
Validate every path the doc references:
rg -no "src/[A-Za-z0-9_./-]+" src/auth/CONTEXT.md | sort -u # referenced paths test -f src/auth/session.ts && echo OK # confirm each exists -
Update these files inline when refactoring the module. A context doc that lags the refactor is worse than none.
Output
- A short, boundary-focused context file inside the subsystem directory
- Stale or central-doc-duplicating content removed or relocated
Verification
- Doc lives inside the subsystem it describes
- Content is boundaries and invariants, not implementation detail or transient notes
- Every referenced file path verified to exist
- No duplication of central docs — one home per fact
- Doc updated in the same change set as the refactor that affected it
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 · 62 lines · 43 tokens per session scan A 13836e9129c4
context-docs is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 43 tokens to every session and 640 once invoked, about $0.0002 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-09-14.
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.