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/topness-msft/callwright/project-contextgit clone --depth 1 https://github.com/topness-msft/callwrightWhat 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.01734 |
| Opus 5 | $0.00000 | $0.00867 |
| Sonnet 5 | $0.00000 | $0.00347 |
| Haiku 4.5 | $0.00000 | $0.00173 |
Grade A, and why
PROJECT-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 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJECT-CONTEXT: Callwright
One-liner
Callwright is a self-hosted, single-user Node.js MCP server that validates, composes, and dispatches outbound calls through Retell, then retrieves and learns from their outcomes.
Architecture principles (immutable unless explicitly revised)
- Reusable behavior belongs in pure
*-core.jsmodules;server.jsand CLI files are thin adapters. - One generic Retell agent receives scenario-neutral dynamic variables; do not create per-scenario agents or scenario-specific dialogue code.
- Spoken phrasing is language data in prompt/phrase assets. AI disclosure is mandatory and non-removable.
place_callis dry-run by default. PII is minimized, values are shared only if asked, and read-backs expose keys/types rather than values.- Automatic retry is bounded and disconnect-based: one retry by default.
Module map / key files
server.js:38-901— HTTP MCP server, tool registration, auth, Retell webhook, health route, and process entry point. This file is over 500 lines; main flow: helpers at 63-116, MCP tools at 118-742, HTTP/webhook routes at 746-876, start at 894-901.dispatch-core.js:151-438— validate/profile/compose/read-back/dispatch pipeline shared by MCP and CLI.setup-core.js:1-434— Retell provisioning, prompt/analysis migration, configuration, and setup status.lang-core.js— runtime language add/verify/update/remove.learn-core.js— profile enrichment and new-scenario candidate staging.retry-core.js— bounded disconnect classification and retry policy.notify-core.js— optional per-call SMS notification.outcome-core.js— canonical custom-status-first outcome interpretation.generic-prompt.md,generic-prompt.ja.md,lang-phrases.json— spoken behavior and language-owned wording.paths.js— mutable-state locations andCALLWRIGHT_DATA_DIR.
Load-bearing / high-blast-radius paths
dispatch-core.js,server.js, andplace_call.schema.jsongate paid calls and personal-data exposure.generic-prompt*.mdcontrols disclosure, transfer behavior, payment limits, and recipient-facing speech.setup-core.jsandupdate-prompt.jsmutate hosted Retell agents; always pin agent and LLM versions.retry-core.jsandserver.jswebhook handling can create additional paid calls; preserve caps and idempotence.paths.jsand volume-resident JSON files contain mutable user state and must survive deploys.
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 · 138 lines · 0 tokens per session scan A 8f9e141682ae
PROJECT-CONTEXT is an agent published in the GitHub repository topness-msft/callwright (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,734 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-31.
Other agents, from other repositories
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
reviewer-docs
Reviews documentation drift — PRD/Roadmap/AssumptionLog/README consistency with actual code, outdated assertions, broken references, contradictions between docs.
audit
🔬 [5維度審計] 深度程式碼審計 — 架構合規 + 安全性 + 品質 + 測試覆蓋 + 文檔同步。.
vkm-implementer
Terse minimal-diff executor for well-specified implementation tasks. Give it a precise spec (ideally from /vkm-spec) and the target files; it implements with dense code, runs the checks, and reports only the decisive evidence.
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…