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 commands/philngt/contextd/contextd-evalgit clone --depth 1 https://github.com/philngt/contextdWhat 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.00000 | $0.02090 |
| Opus 5 | $0.00000 | $0.01045 |
| Sonnet 5 | $0.00000 | $0.00418 |
| Haiku 4.5 | $0.00000 | $0.00209 |
Grade A, and why
contextd-eval 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 yesterday.
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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/contextd-eval — Evaluate Pipeline Effectiveness
Aggregate trace JSON từ nhiều run dưới {project_dir}/.contextd/runs/ → 1 báo cáo Markdown đo hiệu quả wiki: coverage, hallucination rate, top knowledge gaps, context-selector block rate, violation hotspots.
One-shot: 1 lệnh → 1 file Markdown trong
{ws}/reports/. Read-only — KHÔNG sửa runs/. Reference: observability.md, run-trace.schema.json.
Input
| Arg | Required | Notes |
|---|---|---|
--out |
optional | Đường dẫn output. Default: {ws}/reports/contextd-eval-{YYYY-MM-DD}.md. Cùng ngày đã có file → suffix -{HHMMSS}. |
--since |
optional | Filter runs có ts_start ≥ ngày này (YYYY-MM-DD). Default: tất cả. |
--top |
optional | Top-N cho gap/violation/block ranking. Default: 5. |
Bước 0 — Workspace check
Theo workspace-resolution.md Profile A. Set: config_dir (= project_dir), workspace_active, effective_knowledge_root, {ws}. Đồng thời:
- Validate
{project_dir}/.contextd/runs/tồn tại. Nếu không → STOPNo runs found. Chạy /use-contextd ít nhất 1 lần trước..
Bước 1 — Discover runs
Glob {project_dir}/.contextd/runs/*/. Mỗi sub-dir = 1 run. Lưu danh sách run_ids.
Với mỗi run:
- Đọc
run.json(nếu có) — lấyts_start,user_task,workspace_at_run,stages_completed. - Filter:
- Workspace lock: bỏ qua run có
workspace_at_run != workspace_active(KHÔNG leak cross-workspace metric). - Date filter: nếu
--sincecó → bỏ run cóts_start < since.
- Workspace lock: bỏ qua run có
- Đọc các file stage có (
01-planner.json,02-context.json,04-builder.json,05-review.json). Stage thiếu → bỏ qua field tương ứng, không fail. (03-plan-review.jsonđã được gộp vào02-context.jsontừ pipeline v4-stage.)
Nếu danh sách run sau filter = 0 → STOP No runs match filter (workspace={ws}, since={since}).
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.
- yesterday First seen · 242 lines · 0 tokens per session scan A 77866ad9151b
contextd-eval is a command published in the GitHub repository philngt/contextd (29 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,090 tokens. 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 commands, from other repositories
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-x
Audit or improve X/Twitter profile and posting strategy.
help
Category: System Syntax: /help [command|topic].