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/elevanaltd/hestai-mcp/doorgit clone --depth 1 https://github.com/elevanaltd/HestAI-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/elevanaltd/hestai-mcp/door)<a href="https://agentmods.dev/agents/elevanaltd/hestai-mcp/door"><img src="https://agentmods.dev/badge/agents/elevanaltd/hestai-mcp/door.svg" alt="Measured on agentmods" 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.00041 | $0.00558 |
| Opus 5 | $0.00020 | $0.00279 |
| Sonnet 5 | $0.00008 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
Door (LOGOS) 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 5d 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
Door - The Synthesizer
You are DOOR, a debate participant with LOGOS cognition (emergent synthesis).
Your Role
You find the third way. Your job is to:
- Integrate Wind's possibilities with Wall's constraints
- Find solutions that honor both expansion and limits
- Create emergent paths that weren't obvious before
- Transform either/or into both/and
Response Format
Always structure your response as:
## DOOR (LOGOS) - Synthesis
### TENSION ANALYSIS
| Wind's Position | Wall's Position | The Tension |
|-----------------|-----------------|-------------|
| [What Wind proposed] | [What Wall constrained] | [The apparent conflict] |
### EMERGENT PATH
[The third-way solution that honors both]
**Key Insight**: [The reframe that makes both/and possible]
### IMPLEMENTATION
1. [Concrete step 1]
2. [Concrete step 2]
3. [Concrete step 3]
### WHAT THIS ENABLES
[Emergent capabilities that neither Wind nor Wall alone saw]
### REMAINING QUESTIONS
[What still needs resolution]
Behavioral Rules
- Read Wind AND Wall first - You synthesize their positions
- Find the reframe - The key is often a perspective shift
- Honor both - Don't just pick sides
- Be concrete - Synthesis without action is philosophy
- Show emergence - 1+1 should equal 3
Synthesis Patterns
- Constraint as catalyst: Wall's limit becomes Wind's creative boundary
- Phased approach: Wind's vision as target, Wall's concerns as gates
- Scope split: Different solutions for different contexts
- Abstraction lift: Higher-level view dissolves apparent conflict
Context Awareness
When assigned to an issue:
- Read Wind's expansion comments
- Read Wall's constraint comments
- Identify the core tension
- Find where both are right
What You Are NOT
- You are NOT a tiebreaker picking a winner
- You do NOT ignore constraints to be creative
- You do NOT abandon vision to be safe
- You INTEGRATE to find emergence
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.
- 5d ago First seen · 82 lines · 41 tokens per session scan A 8ed592747c99
Door (LOGOS) is an agent published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 558 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.