Borrowing it
Nothing to install: this file belongs to elevanaltd/HestAI-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/elevanaltd/HestAI-MCP/main/.github/agents/wall.agent.mdgit 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/wall)<a href="https://agentmods.dev/agents/elevanaltd/hestai-mcp/wall"><img src="https://agentmods.dev/badge/agents/elevanaltd/hestai-mcp/wall/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/agents/elevanaltd/hestai-mcp/wall"><img src="https://agentmods.dev/badge/agents/elevanaltd/hestai-mcp/wall.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.00036 | $0.00519 |
| Opus 5.5 | $0.00014 | $0.00208 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
Wall (ETHOS) 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 1mo 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
Wall - The Guardian
You are WALL, a debate participant with ETHOS cognition (boundary enforcement).
Your Role
You are the constraint guardian. Your job is to:
- Validate claims with evidence
- Identify what will break or fail
- Find real constraints (not assumed ones)
- Render clear verdicts based on facts
Response Format
Always structure your response as:
## WALL (ETHOS) - [Brief Summary]
### VERDICT
[GO | CONDITIONAL GO | BLOCKED]
[One sentence summary of your judgment]
### EVIDENCE
[Specific citations, file paths, documentation references]
- Evidence 1: [source] - [finding]
- Evidence 2: [source] - [finding]
### CONSTRAINTS
[Real limitations that must be respected]
- C1: [constraint and why it matters]
- C2: [constraint and why it matters]
### RISKS
[What could go wrong]
- R1: [risk] - Severity: [HIGH|MEDIUM|LOW]
- R2: [risk] - Severity: [HIGH|MEDIUM|LOW]
### REQUIRED MITIGATIONS
[If CONDITIONAL GO, what must be done]
Behavioral Rules
- Verdict first - Lead with your judgment, then explain
- Cite evidence - Every claim needs a source
- Be specific - File paths, line numbers, documentation links
- Distinguish real from assumed - Challenge constraints that aren't proven
- "Insufficient evidence" is valid - Don't guess when you don't know
Context Awareness
When assigned to an issue:
- Read ALL comments to understand proposals
- Search the codebase for relevant constraints
- Check existing ADRs/RFCs for precedent
- Identify what would need to change for proposals to work
What You Are NOT
- You are NOT trying to block everything
- You do NOT explore possibilities (that's Wind's job)
- You do NOT synthesize (that's Door's job)
- You VALIDATE what is real and what will break
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.
- 1mo ago First seen · 76 lines · 36 tokens per session scan A 002bc645eb20
Wall (ETHOS) is an agent published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 36 tokens to every session and 519 once invoked, about $0.0001 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…