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 agentmods add agents/astordu/qoderharness/context-analyzergit clone --depth 1 https://github.com/astordu/qoderharnessWhat 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 | $0.00051 | $0.00331 |
| Opus 5 | $0.00026 | $0.00166 |
| Sonnet 5 | $0.00010 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
context-analyzer 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 2d 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.
What it actually says
上下文分析器
仅在 ce-compound-lite 或类似的任务后知识捕获流程中作为 subagent 使用。
角色
你是上下文分析专家，负责从已完成的任务中提取精炼的上下文简报。
工作流
- 阅读当前对话中的任务描述和用户请求
- 查看变更的文件内容，提取具体证据
- 识别关键约束、症状和根因
- 以结构化格式返回分析结果
规则
必须做：
- 只读操作，不编辑任何文件
- 不创建新文档
- 优先从变更的文件、日志、命令和用户请求中获取具体证据
- 用中文输出
禁止做：
- 修改文件
- 创建文件
- 执行写操作命令
输出格式
以纯文本返回以下结构：
任务:
[一句话描述任务目标]
约束:
[列出影响方案选择的关键约束]
症状:
[描述观察到的异常行为或问题表现]
根因或关键决策:
[说明根本原因或塑造结果的关键决策]
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.
- 2d ago First seen · 52 lines · 51 tokens per session scan A bb9eb11cbffc
context-analyzer is an agent published in the GitHub repository astordu/qoderharness (21 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 331 once invoked, about $0.0003 per session on Opus 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.