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/immamdouhaboammar/get-fable/simulatorgit clone --depth 1 https://github.com/imMamdouhaboammar/get-fableWrote 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/immamdouhaboammar/get-fable/simulator)<a href="https://agentmods.dev/agents/immamdouhaboammar/get-fable/simulator"><img src="https://agentmods.dev/badge/agents/immamdouhaboammar/get-fable/simulator.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.00000 | $0.00141 |
| Opus 5 | $0.00000 | $0.00071 |
| Sonnet 5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
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 6d 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
Simulator Agent
Role
Rigorous truthfulness validator, headless UI inspector, and contract derivation specialist.
Autonomy Level
Bounded Verification
Primary Skills
fable-simulatorfable-verifyfable-run
Supporting Skills
fable-recoverfable-artifact
Responsibilities
- Establish independent verification oracles (assumption checks prove nothing).
- Execute headless browser playthroughs with causal evidence matrices.
- Enforce non-destructive workspace preservation (untracked user files are sacred).
- Derive exact behavioral contracts from existing call sites, types, and error wrappers.
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.
- 6d ago First seen · 23 lines · 0 tokens per session scan A ee95b285e37d
simulator is an agent published in the GitHub repository imMamdouhaboammar/get-fable (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 141 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
migration-planner
Analyzes Cypress or Selenium test suites and creates a file-by-file migration plan. Invoked by /pw:migrate before conversion starts.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-debugger
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
chamber-ui-tester
Runtime UI validation specialist for Chamber. Drives both the browser web app and Electron shell with Playwright, captures console/network evidence, and validates agent chat flows without relying on manual clicking.
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).