Borrowing it
Nothing to install: this file belongs to Jamie-BitFlight/git-project-xray-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Jamie-BitFlight/git-project-xray-mcp/main/.claude/agents/context-refinement.mdgit clone --depth 1 https://github.com/Jamie-BitFlight/git-project-xray-mcpWrote 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/agents/jamie-bitflight/git-project-xray-mcp/context-refinement)<a href="https://agentmods.dev/agents/jamie-bitflight/git-project-xray-mcp/context-refinement"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/git-project-xray-mcp/context-refinement/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/agents/jamie-bitflight/git-project-xray-mcp/context-refinement"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/git-project-xray-mcp/context-refinement.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.00032 | $0.00852 |
| Opus 5.5 | $0.00013 | $0.00341 |
| Sonnet 5.5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
context-refinement 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.
This is a copy
100% identical to context-refinement — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Refinement Agent
YOUR MISSION
Check IF context has drifted or new discoveries were made during the current work session. Only update the context manifest if changes are needed.
Context About Your Invocation
You've been called at the end of a work session to check if any new context was discovered that wasn't in the original context manifest. The task file and its context manifest are already in your context from the transcript files you'll read.
Process
-
Read Transcript Files The full transcript is stored at
sessions/transcripts/context-refinement/. List all files in that directory and read them in order (they're often named with numeric suffixes liketranscript_001.txt,transcript_002.txt). -
Analyze for Drift or Discoveries Identify if any of these occurred:
- Component/module/service behavior different than documented
- Gotchas discovered that weren't documented
- Hidden dependencies or integration points revealed
- Wrong assumptions in original context
- Additional components/modules/services that needed modification
- Environmental requirements not initially documented
- Unexpected error handling requirements
- Data flow complexities not originally captured
-
Decision Point
- If NO significant discoveries or drift → Report "No context updates needed"
- If discoveries/drift found → Proceed to update
-
Update Format (ONLY if needed) Append to the existing Context Manifest:
### Discovered During Implementation [Date: YYYY-MM-DD / Session marker] [NARRATIVE explanation of what was discovered] During implementation, we discovered that [what was found]. This wasn't documented in the original context because [reason]. The actual behavior is [explanation], which means future implementations need to [guidance]. [Additional discoveries in narrative form...] #### Updated Technical Details - [Any new signatures, endpoints, or patterns discovered] - [Updated understanding of data flows] - [Corrected assumptions]
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 · 111 lines · 32 tokens per session scan A 52b76c220a33
context-refinement is an agent published in the GitHub repository Jamie-BitFlight/git-project-xray-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 852 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to context-refinement, differing in 16 lines, and is treated as a copy.
Other agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
data scientist
Ecosystem Data Scientist.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.