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/pome223/missionos/e2e-verificationgit clone --depth 1 https://github.com/pome223/missionosWrote 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/pome223/missionos/e2e-verification)<a href="https://agentmods.dev/agents/pome223/missionos/e2e-verification"><img src="https://agentmods.dev/badge/agents/pome223/missionos/e2e-verification.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.00237 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
e2e-verification 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
E2E And Runtime Verification
Runtime changes require runtime verification. Unit tests are useful, but they do not replace a smoke test against the affected production boundary.
For pull-request merge decisions that affect the operator workflow, use
missionos-chat-pr-merge-e2e-checklist.md. It expands this minimum policy into
the required missionos chat path, cross-surface checks, positive and
fail-closed scenarios, screenshots, and release acceptance gate.
Minimum Examples
- CLI: run the command entrypoint with a fixture or real loopback Gateway.
- Gateway: start the server on
127.0.0.1and call the route with a real HTTP client. - Map: generate the HTML artifact from fixture task state and inspect the output path.
- Runtime adapter: run the fixture adapter or an explicitly opt-in SITL smoke.
PR Evidence Format
Every PR with runtime impact should include:
- exact command
- scenario exercised
- production boundary covered
- observed result
- key task ids, fixture ids, status codes, timeline events, or artifact paths
- skipped parts and environment limitations
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 · 30 lines · 0 tokens per session scan A 11248cd889bb
e2e-verification is an agent published in the GitHub repository pome223/missionos (2 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 237 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
gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
ui-tester
Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent.\n\nExamples:\n\n \nContext: User wants to verify that a new…
qa-agent
Persistent-session QA agent for {{targetrepo}}. On each scheduled sweep, discovers PRs opened or pushed since the last check, then checks out each one in its own isolated clone, runs the full verification suite, deploys the change to the test environment, exercises it through the edge, and posts a pass/fail result as…
flaky-test-triage
Daily reusable-session flaky-test triage agent for {{targetrepo}}. On the {{cadence}} schedule, reads CI run history from GitHub, updates a per-test flakiness ledger, and once a test's score reaches {{quarantinethreshold}} opens a quarantine PR (skip + reason, never a deletion) plus a running tracking issue, and posts…