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 commands/rylsherdamz-rgb/stellar-forge/test-e2egit clone --depth 1 https://github.com/rylsherdamz-rgb/stellar-forgeWrote 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/commands/rylsherdamz-rgb/stellar-forge/test-e2e)<a href="https://agentmods.dev/commands/rylsherdamz-rgb/stellar-forge/test-e2e"><img src="https://agentmods.dev/badge/commands/rylsherdamz-rgb/stellar-forge/test-e2e.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 | $0.00000 | $0.00343 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
test-e2e 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
/test-e2e
Run end-to-end tests using the Stellar Agentic Kit.
Usage
/test-e2e <project-path> [network]
network:local(default),testnet
Steps
- Start local Stellar network if needed:
stellar container start local(or check docker-compose) - Deploy contracts if not deployed: invoke
/deploy <project-path> local - Create test accounts and fund them
- Run Playwright tests:
npx playwright test --config <project>/tests/playwright.config.ts - Run Stellar Agentic Kit payment flow tests:
- x402:
node <project>/tests/x402-flow.mjs - MPP:
node <project>/tests/mpp-charge-flow.mjs
- x402:
- Verify contract state via RPC:
node <project>/tests/contract-state.mjs
Expected Results
PLAYWRIGHT: X passed, 0 failed, Y skipped
X402 FLOW: Paid request → 200 OK
MPP FLOW: SAC transfer → confirmed on-chain
STATE: Contract data matches expectations
On Failure
- Capture the specific failure output
- Check the Stellar Quickstart logs:
docker logs stellar-quickstart - Re-spawn the failing agent with the error context
- Max 2 retry attempts
Cleanup
- Write test results to
data/decisions/<date>-e2e-<project-name>.md - Run
/graphify <project> --no-vizto update project graph with test evidence
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 · 38 lines · 0 tokens per session scan A db68d2616955
test-e2e is a command published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 343 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-30.
Other commands, from other repositories
playwright
Write or update Playwright E2E tests following project conventions.
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
index
This documentation covers all available Dashmate CLI commands, their parameters, and behavior.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
plan-spec
仅在人工明确安排 UI 自动化时，根据任务、产品规则或原型生成独立行为 Spec.