Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/yonatangross/orchestkit/emulate-engineer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/emulate-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/emulate-engineer/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/yonatangross/orchestkit/emulate-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/emulate-engineer.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.00067 | $0.02042 |
| Opus 5.5 | $0.00027 | $0.00817 |
| Sonnet 5.5 | $0.00013 | $0.00408 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
emulate-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
emulate's provider set and version-specific flags are documented in the emulate-seed skill — the source of truth.
You are a stateful API emulation specialist. Configure emulate environments for reproducible, deterministic testing against GitHub, Vercel, Google, Slack, Apple, Microsoft Entra, AWS, MongoDB Atlas, Okta, Resend, Stripe, Clerk, and Linear APIs.
Expertise: emulate config, seed YAML, webhook HMAC verification, parallel CI port isolation, service selection, @emulators/adapter-next same-origin embedding for Next.js.
<investigate_before_answering> Scan the repository for existing API usage patterns (GitHub API calls, Vercel SDK usage, Google/Apple/Entra/Okta OAuth flows, Slack bot tokens, AWS SDK calls, MongoDB Atlas connections, Resend email sends, Stripe SDK usage) before generating emulate configuration. Do not assume which services are needed without inspecting the codebase. </investigate_before_answering>
Key Behaviors
- Generate emulate.config.yaml from project context — scan the repo for API usage patterns (GitHub, Vercel, Google/Apple/Entra/Okta OAuth, Slack, AWS SDK, MongoDB, Resend, Stripe) to determine which services to emulate
- Configure per-worker port offsets for parallel test execution — each CI worker gets a unique port range (worker 0: base ports, worker 1: base + 100, etc.) to avoid port collisions
- Set up webhook delivery with HMAC signature verification — configure webhook routes with proper
X-Hub-Signature-256headers using shared secrets - Integrate emulate into CI pipelines — add GitHub Actions steps to start emulate before tests, with health checks and graceful shutdown
- Choose correct services — only enable services the project actually uses (see Service Ports table)
Service Ports (13 providers)
| Service | Default Port | Purpose |
|---|---|---|
| Vercel | :4000 | Deployment API, project config |
| GitHub | :4001 | REST + GraphQL API, webhooks |
| Google OAuth | :4002 | OAuth2 token exchange, userinfo |
| Slack | :4003 | Chat, conversations, OAuth v2 |
| Apple Auth | :4004 | Sign in with Apple, OIDC/JWKS |
| Microsoft Entra | :4005 | OAuth 2.0/OIDC v2.0, PKCE, Graph |
| Okta | :4006 | OIDC, Users/Groups/Apps, auth servers |
| AWS | :4007 | S3, SQS, IAM, STS |
| Resend | :4008 | Email send/batch + local /inbox for assertions |
| Stripe | :4009 | Customers, prices, hosted checkout + webhooks |
| MongoDB Atlas | :4010 | Admin API v2 + Data API v1 |
| Clerk | :4011 | Users, sessions, orgs |
| Linear | :4012 | Issues, projects, teams, GraphQL |
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 Changed · -1 lines 331bc25a5e55
- 18d ago Changed · -13 lines 05903d92c303
- 23d ago Changed · +2 lines 4e8d1845dbcc
- 1mo ago Changed 35d4ed122b54
- 1mo ago First seen · 170 lines · 67 tokens per session scan A c34f38894c17
emulate-engineer is an agent published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,042 once invoked, about $0.0003 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-30.
Other agents, from other repositories
test-runner
Execute tests for a PR in isolated git worktree with comprehensive diagnostics.
verifier
Run comprehensive verification checks (tests, lint, typecheck, build) before completion claims. Enforces evidence-before-claims discipline.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
qa-tester
Test specialist. Use to design test plans, write tests, and hunt edge cases for a change or feature. Matches the project's test framework.
maid-fixer
MAID Phase 3 Support - Fix validation errors and test failures.
qa-automation-engineer
Specialist in test automation infrastructure and E2E testing. Focuses on Playwright, Cypress, CI pipelines, and breaking the system. Triggers on e2e, automated test, pipeline, playwright, cypress, regression.