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 map-appgit 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/map-app)<a href="https://agentmods.dev/skills/atagon-gmbh/kogiqa-mcp/map-app"><img src="https://agentmods.dev/badge/skills/atagon-gmbh/kogiqa-mcp/map-app/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/map-app"><img src="https://agentmods.dev/badge/skills/atagon-gmbh/kogiqa-mcp/map-app.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.00033 | $0.00230 |
| Opus 5.5 | $0.00013 | $0.00092 |
| Sonnet 5.5 | $0.00007 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
map-app 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
Map and document an app
Crawl an app breadth-first and produce a structured document of what it contains.
Workflow
browser_navigateto the start URL.- On each page, capture the title (
browser_get_page_title), the visible content (browser_get_page_text), the links/buttons (browser_list_clickable), and the inputs (browser_list_page_inputs). - Follow internal links up to the requested depth, skipping external hosts, auth redirects, and destructive actions (logout, delete). Track visited URLs to avoid loops.
- Note any console errors encountered with
browser_get_console_log.
Output
Write a Markdown document with one section per page: the URL, a one-line summary, its purpose, its main interactive elements, and any problems found. Include a short table of contents at the top. State the crawl depth and any pages you deliberately skipped.
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 · 25 lines · 33 tokens per session scan A 7f4015fd6af6
map-app is a skill published in the GitHub repository atagon-GmbH/kogiqa-mcp (96 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 230 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 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.
apitap
ApiTap gives AI agents cheap access to web data through three layers.
x-use-inbox
Read X direct messages, triage inbox and request folders, send contextual reviewed messages, and inspect notifications with x-use. Use for unread chats, conversation search or replies, individual DMs, and All or Mentions notifications; use x-use-engage for public-post engagement and profile outreach research.
x-use
Install, register, and configure x-use, the browser-native MCP server for X (Twitter) automation that needs no X API key. Covers pip install, MCP client registration for Claude Desktop, Claude Code, Codex, Cursor and Windsurf, cookie-based account setup, keywords, and persona. Use when the user wants to set up x-use…
browser-automation
Control the user's real browser via Browser Controller. Use when asked to interact with web pages, test UIs, fill forms, or read page content.
chrome-bridge
Recipes for the user's real, logged-in Chrome through the chrome-bridge MCP tools and the zero-token chrome-bridge CLI. Use when a browser task needs a multi-step recipe — a form "until the email arrives", a checkout with a test card, a pixel/GTM check, a cookie-banner audit, redirects after a migration, a page…