simulator

simulator is an agent for Claude Code from Zeekeey-jpeg/LeRoy-HQ. It costs 70 tokens per session (2,041 once invoked), scanned A, original, MIT.

A protocol-compliance testing agent that sends test questions and checks whether responses meet defined rules. Compliance metrics are measurements such as correctness, response time, memory recall, and required actions.

In plain words
What is it for?
It helps run full or batch simulations, test enforcement fixes, capture responses and state changes, score five compliance areas, and export validation results.
Why use it?
It helps detect regressions and verify that protocol changes still enforce the expected behavior.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; names the TodoWrite tool.

Good fit It helps run full or batch simulations, test enforcement fixes, capture responses and state changes, score five compliance areas, and export validation results.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zeekeey-jpeg/leroy-hq/simulator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Zeekeey-jpeg/LeRoy-HQ

Made for: Claude Code.

Wrote 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.

agentmods badge for simulator

README.md
[![agentmods](https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/simulator.svg)](https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/simulator)
Your own site
<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/simulator"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/simulator.svg" alt="Measured on agentmods" height="20"></a>
Per session 70 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,041 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.02041
Opus 5 $0.00035 $0.01020
Sonnet 5 $0.00014 $0.00408
Haiku 4.5 $0.00007 $0.00204

Measured 8d ago against content hash 99f13ac258d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

simulator 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 8d 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.

core/agents/simulator.md · 262 lines

How it starts

The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Simulator Agent - Protocol Compliance Testing

Purpose

Execute protocol compliance tests by submitting questions and validating responses against 5 compliance metrics.

When to Use

  • Full simulation runs (250-question validation)
  • Batch testing of enforcement fixes
  • Regression testing after protocol changes
  • Validation of Phase 1/2/3 enforcement implementations

Capabilities

  • Submit questions to Claude (simulated user requests)
  • Capture full response including timings, state changes, task logs
  • Validate gate output, memory recall, agent spawn, response time, answer correctness
  • Export results in validation framework JSON format

Tools Available

  • Read - Load questions from test-questions.json, read state.json for validation
  • Bash - Execute timing measurements, state snapshots
  • Grep/Glob - Search for patterns in responses
  • TodoWrite - Track batch progress (optional)

Input Format

Receives batch assignment with 5-25 questions:

{
  "batch_id": 1,
  "questions": [
    {
      "question_id": "Q001",
      "question": "What is Protocol Enforcement v5.6?",
      "category": "decisions",
      "source_file": "Decisions/Protocol-Enforcement-v5.6.md",
      "expected_answer": "Information about Protocol Enforcement v5.6",
      "complexity": "trivial"
    }
    // ... more questions
  ],
  "output_file": ".claude/session/batch-1-results.json"
}

Execution Protocol

1. Initialize Batch

- Read questions from input
- Create state snapshot (baseline)
- Initialize results array
- Start batch timer

2. Per Question Execution

For each question in batch:

A. Pre-Question Setup

  • Snapshot current state.json
  • Record start timestamp
  • Clear any stale enforcement flags

B. Submit Question

  • Format as natural user prompt
  • Submit to Claude (simulated request)
  • Capture full response text

C. Capture Response Data

  • Record end timestamp (calculate duration)
  • Read updated state.json (memory_system.last_recall, notes_loaded)
  • Extract task log (check for Task tool calls with subagent_type)
  • Extract answer content (text after [MEMORY] block if present)

Read the full file on GitHub · 262 lines

Changes

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.

  1. 8d ago First seen · 262 lines · 70 tokens per session scan A 99f13ac258d7

Subscribe to this mod's changes

simulator is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 15d ago), licensed MIT. It adds 70 tokens to every session and 2,041 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

session-reviewer

Use this agent between waves or at session end to verify work quality against the session plan. Checks implementation correctness, test coverage, TypeScript health, security basics, and issue tracking accuracy. Context: Impl-Core wave is complete, coordinator needs quality check before Impl-Polish. user: "Impl-Core…

Kanevry/session-orchestrator · 165 tokens

test-writer

Use this agent to close NAMED test gaps and to consolidate redundant tests. It writes the specific missing test, and it deletes, merges, or parameterises tests that do not earn their keep. Context: Quality wave named one concrete gap — the invoice service never exercises the declined-payment branch. user: "The invoice…

Kanevry/session-orchestrator · 281 tokens

ux-evaluator

Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…

Kanevry/session-orchestrator · 199 tokens

qa-strategist

Use this agent for read-only test-coverage gap analysis between waves. Identifies missing boundary cases, error paths, and integration gaps not caught by happy-path tests. Context: Impl-Core shipped a new auth flow with 6 unit tests. user: "Check the test coverage gaps." assistant: "I'll dispatch qa-strategist to…

Kanevry/session-orchestrator · 111 tokens

project-quality-gate

Use this agent when you need to verify a repo meets quality standards before a release, merge, or deployment decision. Context: The session is about to close and the coordinator wants a final quality check. user: "Run the quality gate checks" assistant: "I'll use the project-quality-gate agent to verify tests pass…

Kanevry/session-orchestrator · 0 tokens

test-architect

Use after the worktree is prepared to write all failing acceptance tests from the structure. Tests form the immutable scope fence for implementation. Operates inside the implement phase as a sub-step before the implementer runs.

bostonaholic/team · 46 tokens