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.
git 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/commands/atagon-gmbh/kogiqa-mcp/smoke-test)<a href="https://agentmods.dev/commands/atagon-gmbh/kogiqa-mcp/smoke-test"><img src="https://agentmods.dev/badge/commands/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/commands/atagon-gmbh/kogiqa-mcp/smoke-test"><img src="https://agentmods.dev/badge/commands/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.00013 | $0.00211 |
| Opus 5.5 | $0.00005 | $0.00084 |
| Sonnet 5.5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
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 the flow in $ARGUMENTS.
Interpret the arguments as a URL followed by the flow to exercise. Walk each step in the
kogiQA browser, asserting state between steps with browser_has_text and
browser_has_button. Report each step as pass/fail with the evidence returned. Stop and
report clearly if a step fails. Finish with a check for console errors.
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 · 13 lines · 13 tokens per session scan A 62551224da16
smoke-test is a command published in the GitHub repository atagon-GmbH/kogiqa-mcp (96 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 211 once invoked, about $0.0001 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 commands, from other repositories
verify-pr
Verify a PR's frontend changes through browser automation.
record
Record browser actions into a test definition.
verify
Verify a feature works through automated testing.
test-run
Run E2E tests with qa-use CLI.
multi-page
Smoke test multiple pages in parallel using alethiatellparallel.
smoke
Quick Alethia smoke test — navigate and assert the page loads.