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 TierZeroAI/tierzero-cursor --skill tierzero-fetchgit 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-fetch)<a href="https://agentmods.dev/skills/tierzeroai/tierzero-cursor/tierzero-fetch"><img src="https://agentmods.dev/badge/skills/tierzeroai/tierzero-cursor/tierzero-fetch/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/tierzeroai/tierzero-cursor/tierzero-fetch"><img src="https://agentmods.dev/badge/skills/tierzeroai/tierzero-cursor/tierzero-fetch.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.00078 | $0.00578 |
| Opus 5.5 | $0.00031 | $0.00231 |
| Sonnet 5.5 | $0.00016 | $0.00116 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
tierzero-fetch 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 1mo 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
TierZero: Fetch Context
Load saved TierZero context (a chat thread, investigation, or artifact) so the agent can act on it.
When to use
- The user pastes a TierZero URL (
https://app.tierzero.ai/chat/c/...orhttps://app.tierzero.ai/investigations/...). - The user pastes a bare artifact UUID (e.g.
bf904904-afdc-4cf2-94d8-76a4a8bb4f75). - The user says "load that investigation" / "pull in the context from TierZero" / similar.
How to call
Use the tierzero_fetch_context MCP tool exposed by the tierzero MCP server registered by this plugin.
Arguments:
url(string, required): the chat URL, investigation URL, or artifact UUID.include_sources(bool, optional, defaultfalse): set totrueonly when the user asks for source-by-source breakdowns or you need to cite specific log lines / traces.
Supported inputs:
| Type | Example |
|---|---|
| Chat URL | https://app.tierzero.ai/chat/c/<GlobalID> |
| Investigation URL | https://app.tierzero.ai/investigations/<GlobalID> |
| Artifact UUID | bf904904-afdc-4cf2-94d8-76a4a8bb4f75 |
After the call
Parse the response and surface what's relevant for the current task:
- Conversations — walk the messages (use
messageTypeandoutput); summarize the conclusion, then note any open questions. - Investigations — present the
outputJsonresult; quote findings, list evidence sources. - Artifacts — show the artifact
valueandtype; if it's a log/metric snapshot, summarize what it contains.
Only include source metadata if the user explicitly asks for it (and call with include_sources: true). Otherwise it's noise.
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.
- 1mo ago First seen · 48 lines · 78 tokens per session scan A 607ecef715e2
tierzero-fetch is a skill published in the GitHub repository TierZeroAI/tierzero-cursor (0 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 578 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.