investigate

A command for asking TierZero to investigate connected production systems in plain English.

In plain words
What is it for?
It is for checking incidents, service health, request latency, unusual traffic, and whether recent automated builds or deployments failed.
Why use it?
It turns a question about a live service into an investigation using production information such as errors, response times, deployments, and failed build jobs.

Command

Install

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.

agentmods
npx agentmods add commands/tierzeroai/tierzero-cursor/investigate
Clone the repo
git clone --depth 1 https://github.com/TierZeroAI/tierzero-cursor
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 311 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00026 $0.00311
Opus 5 $0.00013 $0.00156
Sonnet 5 $0.00005 $0.00062
Haiku 4.5 $0.00003 $0.00031

Measured yesterday against content hash 2e1ac694b559, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

investigate 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.

plugins/tierzero/commands/investigate.md · 32 lines

What it actually says

/investigate

Run a TierZero investigation against connected production systems.

The arguments after /investigate are the user's natural-language query.

Steps

  1. Treat everything the user typed after /investigate as the investigation query.
  2. If the query is empty, ask the user what they want to investigate, then stop.
  3. Call the tierzero_ask tool on the tierzero MCP server with that query as the query argument.
  4. Wait for the response, then summarize the findings tied to the user's current work.
  5. Surface any TierZero investigation URL returned in the result so the user can drill in.
  6. If the call fails with an authentication error, tell the user to open Cursor Settings → MCP → tierzero and click Authorize (or re-authorize), then retry.

Tips for a good query

  • Name the service or component, not "the API"
  • Include a time window ("last hour", "since the 13:42 UTC deploy")
  • State the symptom (errors, latency, drop in traffic)

Examples

  • /investigate what errors hit payment-service in the last hour?
  • /investigate p95 latency for /api/checkout over the last 24h, flag anomalies
  • /investigate did any github actions runs for the api repo fail today?
Changes

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.

  1. yesterday First seen · 32 lines · 26 tokens per session scan A 2e1ac694b559

Subscribe to this mod's changes

investigate is a command published in the GitHub repository TierZeroAI/tierzero-cursor (0 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 311 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-31.