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 skills/ggprompts/tabzchrome/integrationnpx skills add GGPrompts/TabzChrome --skill integrationgit clone --depth 1 https://github.com/GGPrompts/TabzChromeWrote 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/ggprompts/tabzchrome/integration)<a href="https://agentmods.dev/skills/ggprompts/tabzchrome/integration"><img src="https://agentmods.dev/badge/skills/ggprompts/tabzchrome/integration.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.1 | $0.00026 | $0.00577 |
| Opus 5 | $0.00013 | $0.00289 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
integration 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TabzChrome Integration
Help users integrate their projects with TabzChrome terminals.
When to Use
- Creating project dashboards with terminal buttons in markdown
- Adding "Run in Terminal" buttons to web pages
- Creating CLI tools that queue commands to TabzChrome
- Building prompt libraries with fillable templates
- Programmatically spawning terminal tabs
Integration Methods
| Method | Auth | Best For |
|---|---|---|
Markdown tabz: links |
None | Project dashboards, docs in file viewer |
HTML data-terminal-command |
None | Static buttons on web pages |
| WebSocket + websocat | File token | CLI/tmux workflows |
| WebSocket + JS | API token | Prompt libraries, web apps |
| POST /api/spawn | Token | Creating new terminal tabs |
Quick Start
First, ask which integration the user needs:
questions:
- question: "Which TabzChrome integration methods do you need?"
header: "Integration"
multiSelect: true
options:
- label: "Markdown Links"
description: "tabz: protocol for project dashboards in file viewer"
- label: "HTML Buttons"
description: "data-terminal-command for 'Run in Terminal' buttons"
- label: "CLI/Scripts"
description: "WebSocket via websocat for shell scripts"
- label: "Web App JS"
description: "JavaScript WebSocket for prompt libraries"
- label: "Spawn API"
description: "POST /api/spawn to create new tabs"
Then provide the relevant reference:
| Selection | Reference |
|---|---|
| Markdown Links | references/markdown-links.md |
| HTML Buttons | references/html-integration.md |
| CLI/Scripts | references/cli-websocket.md |
| Web App JS | references/javascript-api.md |
| Spawn API | references/spawn-api.md |
Authentication Summary
| Context | Method |
|---|---|
| CLI / Scripts | TOKEN=$(cat /tmp/tabz-auth-token) |
| Extension Settings | Click "API Token" → "Copy Token" |
| External web pages | User pastes token (stored in localStorage) |
What ships with it
6 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.
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 · 85 lines · 26 tokens per session scan A c44f8446ac68
integration is a skill published in the GitHub repository GGPrompts/TabzChrome (146 stars, last pushed 12d ago), licensed MIT. It adds 26 tokens to every session and 577 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…