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.
git clone --depth 1 https://github.com/Dexter-DAO/opendexter-ideWrote 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/commands/dexter-dao/opendexter-ide/setup-opendexter)<a href="https://agentmods.dev/commands/dexter-dao/opendexter-ide/setup-opendexter"><img src="https://agentmods.dev/badge/commands/dexter-dao/opendexter-ide/setup-opendexter/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/commands/dexter-dao/opendexter-ide/setup-opendexter"><img src="https://agentmods.dev/badge/commands/dexter-dao/opendexter-ide/setup-opendexter.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.00022 | $0.00766 |
| Opus 5 | $0.00011 | $0.00383 |
| Sonnet 5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
setup-opendexter 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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install OpenDexter MCP
Set up the local proxy for OpenDexter's hosted governed x402 runtime. Setup never creates or enables a local payment wallet.
Steps
- Run the guided installer:
npx @dexterai/[email protected] setup
To target one client:
npx @dexterai/[email protected] install --client cursor
Supported client names are cursor, claude-code, codex, vscode,
windsurf, and gemini-cli. Codex uses TOML, so the installer prints its
exact block instead of editing it.
- Connect the proxy to the hosted governed runtime:
npx @dexterai/[email protected] connect
npx @dexterai/[email protected] connect status
The connection stores an OAuth bearer. It does not by itself prove an active
grant. The bearer targets https://open.dexter.cash/mcp with exact requested
scope vault. Dexter's signed top-level dexter_surface token claim is
separate authority evidence, not a requested OAuth scope. Status must report the exact live grant, principal,
limits, remaining capacity, expiry, scopes, active role, and revocation evidence
before payment authority is treated as active.
- Verify
tools/list. The exact roster is:
x402_search, x402_check, x402_fetch, x402_status, x402_access,
x402_wallet, and dexter_portfolio.
- Test the anonymous non-paying path:
x402_search({"query":"extract tables from a PDF"})
Then call x402_check for the selected exact URL, method, and body. A search
result does not authorize payment. A non-GET check needs separate approval for
that exact probe; probe approval is not payment approval, and the request is
never automatically retried after possible dispatch.
- For a paid action, use a connected check. Keep its returned
intentIdopaque, show the exact current terms, obtain approval formaxAmountAtomic, and callx402_fetchonce with only those two fields.
If the fetch result is uncertain, call x402_status with the same intentId.
Never retry the consequential fetch merely because its result or bearer
response was ambiguous.
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.
- 9d ago First seen · 86 lines · 22 tokens per session scan A 1935f0e4bcb3
setup-opendexter is a command published in the GitHub repository Dexter-DAO/opendexter-ide (2 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 766 once invoked, about $0.0001 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-31.
Other commands, from other repositories
api-mock
You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
performance-optimization
Orchestrate end-to-end application performance optimization from profiling to monitoring.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
data-driven-feature
Build features guided by data insights, A/B testing, and continuous measurement.