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 atagon-GmbH/kogiqa-mcp --skill smoke-testgit clone --depth 1 https://github.com/atagon-GmbH/kogiqa-mcpWrote 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/atagon-gmbh/kogiqa-mcp/smoke-test)<a href="https://agentmods.dev/skills/atagon-gmbh/kogiqa-mcp/smoke-test"><img src="https://agentmods.dev/badge/skills/atagon-gmbh/kogiqa-mcp/smoke-test/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/atagon-gmbh/kogiqa-mcp/smoke-test"><img src="https://agentmods.dev/badge/skills/atagon-gmbh/kogiqa-mcp/smoke-test.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.00044 | $0.00273 |
| Opus 5.5 | $0.00018 | $0.00109 |
| Sonnet 5.5 | $0.00009 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
smoke-test 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 2d 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
Smoke-test a user flow
Walk through a named user flow and verify the expected outcome.
Workflow
- Confirm the flow, the entry URL, and the expected end state with the user if anything is ambiguous.
browser_navigateto the entry URL.browser_get_page_titleandbrowser_list_clickableto orient yourself before acting.- Perform each step with
browser_type,browser_click,browser_select, andbrowser_keypress. Usebrowser_has_text,browser_has_button, andbrowser_has_inputto assert state between steps. - At the end, verify the expected result, for example
browser_get_page_textorbrowser_has_textfor a confirmation message. browser_get_console_logonce at the end to catch silent errors.
Reporting
Report each step as pass/fail with the evidence the tool returned. If a step fails, stop and report the failing step, what you expected, and what you saw. Do not silently skip steps.
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.
- 2d ago First seen · 27 lines · 44 tokens per session scan A f5c35428b96b
smoke-test is a skill published in the GitHub repository atagon-GmbH/kogiqa-mcp (96 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 273 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
alethia
Use Alethia, a patent-pending agent-native software runtime for executing and verifying application workflows, to interact with a real browser, run E2E checks, enforce safety policies, audit accessibility or security, and export signed evidence. Requires the @vitronai/alethia MCP server to be configured. Trigger…
browser-viz-verify
Verifies that a NetClaw-generated visualization HTML file (three.js, canvas, drawio, UML, markmap) actually renders correctly — screenshot, console-error check, and an optional Lighthouse audit. Use immediately after generating any browser-based visualization output, to close the QA gap that otherwise requires a human…
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
flutter-mcp-toolkit-control
Drive a running Flutter app — tap, scroll, type, fill forms, hot-reload, navigate. Use when you need to interact with the UI.
flutter-mcp-e2e-harness
Use this skill when writing or running repeatable E2E scenarios for Flutter apps as checked-in Dart with the fluttermcpharness package (packages/harness) — build/launch the app, attach to its VM service, drive widgets (snapshot/tap/enter text) and assert without MCP; also covers the repo showcase launcher (make…