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/tierzeroai/tierzero-cursor/tierzero-investigatenpx skills add TierZeroAI/tierzero-cursor --skill tierzero-investigategit clone --depth 1 https://github.com/TierZeroAI/tierzero-cursorWrote 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/tierzeroai/tierzero-cursor/tierzero-investigate)<a href="https://agentmods.dev/skills/tierzeroai/tierzero-cursor/tierzero-investigate"><img src="https://agentmods.dev/badge/skills/tierzeroai/tierzero-cursor/tierzero-investigate.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 | $0.00117 | $0.00900 |
| Opus 5 | $0.00059 | $0.00450 |
| Sonnet 5 | $0.00023 | $0.00180 |
| Haiku 4.5 | $0.00012 | $0.00090 |
Grade A, and why
tierzero-investigate scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
This plugin registers TierZero as an MCP server (`tierzero`) in Cursor. Call the MCP tools directly — do **not** shell out to curl or wrap them in scripts. How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TierZero: Production Investigation Skill
Query production telemetry through TierZero's MCP server and run end-to-end investigations across logs, metrics, traces, CI/CD runs, and knowledge bases.
When to use
TRIGGER when:
- The user is debugging a production issue, error, or alert
- The user references an incident, alert page, or recent deploy
- The user asks "what's happening with X?" / "is service Y healthy?" / "did the deploy break anything?"
- A code change touches a hot path and you don't yet know what calls it or how often
- A PR review hinges on whether something is actually broken in prod
- The user pastes a service name, error string, stack trace, or alert from a real environment
- Any task where understanding real traffic, error rates, latency, or usage would change the answer
DO NOT trigger for pure unit tests, doc-only changes, or local-dev questions where production data is irrelevant.
How to call
This plugin registers TierZero as an MCP server (tierzero) in Cursor. Call the MCP tools directly — do not shell out to curl or wrap them in scripts.
Primary tools:
tierzero_ask— kicks off an investigation and returns a grounded answer. Pass a singlequeryargument in plain English. Be specific (service name, time range, symptom).tierzero_fetch_context— load a TierZero conversation, investigation, or artifact by URL or UUID. Use thetierzero-fetchskill when this applies.
Other tools the TierZero MCP server exposes are also available — check the server's tool list when you need more specific access (raw logs, traces, CI runs).
Writing good queries
A good query for tierzero_ask:
- Names the service or component (e.g.
payment-service, not "the API") - Specifies a time window (e.g. "last 30 minutes", "since 14:00 UTC", "during the deploy at 13:42")
- States the symptom (errors, latency, drop in traffic, unexpected log line)
- Mentions the integration if relevant (Datadog, Sentry, GitHub Actions, etc.)
Examples:
What errors occurred in payment-service in the last hour?Show p95 latency for /api/checkout over the last 24h and flag anomalies.Did any GitHub Actions workflows for the api repo fail today?Has the rate of 5xx on auth-service changed since the deploy at 13:42 UTC?
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.
- 4d ago First seen · 69 lines · 117 tokens per session scan A af84810cec7a
tierzero-investigate is a skill published in the GitHub repository TierZeroAI/tierzero-cursor (0 stars, last pushed 3mo ago), licensed MIT. It adds 117 tokens to every session and 900 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…