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 instructions/mozilla-ocho/tabstack-cli/agents-mdgit clone --depth 1 https://github.com/Mozilla-Ocho/tabstack-cliWhat 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 | $0.02600 | $0.02600 |
| Opus 5 | $0.01300 | $0.01300 |
| Sonnet 5 | $0.00520 | $0.00520 |
| Haiku 4.5 | $0.00260 | $0.00260 |
Grade A, and why
tabstack-cli AGENTS.md 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 yesterday.
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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using tabstack from an AI agent
This document tells an LLM agent how to drive the tabstack CLI correctly. It is
a reference, not a tutorial: every command, flag, input format, output shape,
and failure mode is listed so you can call the tool without guessing.
TL;DR for agents
- Always pass
-o jsonso output is deterministic and parseable. Without it, output is pretty-printed on a TTY and only switches to JSON when piped. - Provide an API key via the
TABSTACK_API_KEYenv var (preferred for automation) or--api-key. Do not rely on an interactiveauth loginprompt. - Branch on the exit code, not on stderr text:
0ok,1runtime/network,2bad input or missing key,3API error or task failure. extract json/generate jsonreturn exactly the JSON shape your schema describes. Nothing is wrapped or reshaped. Validate your schema before calling; malformed schemas fail locally with exit2.automateandresearchstream. In-o jsonthey emit NDJSON (one JSON object per line); read line by line, do notJSON.parsethe whole output.
Setup
export TABSTACK_API_KEY="<key>" # preferred for non-interactive use
# optional:
export TABSTACK_BASE_URL="<url>" # override API root
Key resolution precedence (highest first): --api-key flag → TABSTACK_API_KEY
→ config file (~/.config/tabstack/config.toml). If no key is found, commands
that hit the API exit 2 (non-retryable config error) with a clear message.
Global flags (valid on every command)
| Flag | Effect |
|---|---|
-o, --output pretty|json |
Set json for agents. Default auto-detects (pretty on TTY, json when piped). |
--api-key <key> |
API key, overrides env + config. |
--base-url <url> |
API root, overrides env + config. |
--no-color |
Disable ANSI colour (also honours NO_COLOR). Irrelevant under -o json. |
--timeout <dur> |
Timeout for non-streaming calls only, e.g. 30s, 2m. Ignored by automate/research. |
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.
- yesterday First seen · 225 lines · 2,600 tokens per session scan A 1367e56af98d
tabstack-cli AGENTS.md is an instructions file published in the GitHub repository Mozilla-Ocho/tabstack-cli (11 stars, last pushed 26d ago), licensed MIT. It adds 2,600 tokens to every session, about $0.0130 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.