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 skills add granoflow/granoflow-mcp-server --skill granoflow-e2e-test-campaigngit clone --depth 1 https://github.com/granoflow/granoflow-mcp-serverWrote 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/skills/granoflow/granoflow-mcp-server/granoflow-e2e-test-campaign)<a href="https://agentmods.dev/skills/granoflow/granoflow-mcp-server/granoflow-e2e-test-campaign"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-e2e-test-campaign/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/skills/granoflow/granoflow-mcp-server/granoflow-e2e-test-campaign"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-e2e-test-campaign.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.04810 |
| Opus 5 | $0.00034 | $0.02405 |
| Sonnet 5 | $0.00013 | $0.00962 |
| Haiku 4.5 | $0.00007 | $0.00481 |
Grade A, and why
granoflow-e2e-test-campaign 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 10d 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Granoflow E2E Test Campaign
Use this Skill when the user requires running end-to-end UI journeys as a
campaign (for example: Run e2e campaign, 开始 E2E 战役, 开始端到端测试,
开始最终交付 / 开始完整交付), or when最终交付 has entered lifecycle stage
e2e_campaign per full-delivery-acceptance.
This is the E2E leg of最终交付 and the final test stage before
project_complete: real UI human_path coverage of daily user operations
from Project Work, with live-window screenshots under temp/ and auto-drive
fixes until green (or green_with_external_residuals).
Start gate: integration_gate is complete (multi-milestone path after full
unit + portfolio IT) or waived_single_milestone (exactly one feature
milestone; Layer B already covered IT). E2E coverage is always full-project
(never narrowed to "what we touched"), so formal campaign artifacts set
e2e_scope: full_project_e2e. Task-local or diagnostic evidence may be labeled
feature_e2e or journey_e2e, but those labels never satisfy this campaign or
full_user_path. Detail: e2e-test-campaign-contract.
After campaign start, the E2E loop is agent auto-drive for both
interactive and unattended project modes: do not ask ordinary phase
confirmations, “run next journey?”, or “capture this screenshot?” questions.
Not This Skill
| Concern | Owner |
|---|---|
| Task-local: judge unit sufficiency, add ≤2 tests, do not run | granoflow-agent-workflow Task Integration Test Policy |
| service_path integration, shared-session I/O without UI | granoflow-integration-test-campaign |
| Copy-only / 文字验证: no automated tests | user-visible-copy-boundary.md |
| Single-task Analysis/Plan/run | granoflow-task-orchestrator + granoflow-agent-workflow |
| Create product milestones/tasks portfolio | granoflow-portfolio-orchestrator |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 557 B
- references/e2e-campaign-closing-summary-template.md 3.5 KB
- references/e2e-campaign-closing-summary.md 5.8 KB
- references/e2e-evidence-pack.md 8.0 KB
- references/e2e-host-capabilities.md 13 KB
- references/e2e-suite-orchestration.md 6.7 KB
- references/e2e-test-campaign-contract.md 11 KB
- references/e2e-user-flow-coverage.md 11 KB
- scripts/lint_e2e_campaign_artifacts.py 125 KB runs code
- scripts/probe_execution_hosts.py 9.2 KB runs code
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.
- 10d ago First seen · 395 lines · 67 tokens per session scan A b6042963c320
granoflow-e2e-test-campaign is a skill published in the GitHub repository granoflow/granoflow-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 4,810 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.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…