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/zoominfo/zoominfo-mcp-plugin/tech-stack-snapshotnpx skills add Zoominfo/zoominfo-mcp-plugin --skill tech-stack-snapshotgit clone --depth 1 https://github.com/Zoominfo/zoominfo-mcp-pluginWrote 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/zoominfo/zoominfo-mcp-plugin/tech-stack-snapshot)<a href="https://agentmods.dev/skills/zoominfo/zoominfo-mcp-plugin/tech-stack-snapshot"><img src="https://agentmods.dev/badge/skills/zoominfo/zoominfo-mcp-plugin/tech-stack-snapshot.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.00158 | $0.03705 |
| Opus 5 | $0.00079 | $0.01852 |
| Sonnet 5 | $0.00032 | $0.00741 |
| Haiku 4.5 | $0.00016 | $0.00370 |
Grade A, and why
tech-stack-snapshot 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Stack Snapshot
Per-company tech-stack snapshot grouped by category, with displacement angles for competitive tools and integration angles for partner tools — anchored on the user's GTM context. Resolves mixed-identifier inputs, queries search_companies with techAttributeTagList to check each product in a curated universe, and presents both the detected stack and the gaps honestly.
How it works
search_companies accepts techAttributeTagList (tech-product IDs) as a filter:
search_companies(
companyId="<input IDs, comma-separated>",
techAttributeTagList=<one product ID>,
pageSize=<N>
) → returns subset of input companies that have that product tagged
Iterate over a curated universe of ~30–50 high-relevance tech products → build a company × product matrix → group by category and pair with GTM-context-anchored plays.
The bar
- Resolution accuracy 100% — every input bucketed; never silently picked.
- Detections are binary and verified — ✅ comes from a non-zero
search_companiesresult; ❌ means no tag. Never invent presence. - Output is grouped by category.
- Recommended plays anchor on GTM context.
- Coverage gaps surfaced honestly — absence = "no tag detected", not "no tool used."
Always-on context: get_gtm_context
Every run calls get_gtm_context(detailed: true). Drives:
- Which categories are in scope (sales-focused vs. dev-focused).
- Which detected tools map to displacement vs. integration angles.
- Framing of recommended plays (anchored on specific value props).
Scope
Snapshots are company-level. Per-person tech-skill data is out of scope.
Input
- Companies (required) — list of ZI IDs / names / domains / mixed CSV.
- Categories of interest (optional) — any of:
sales,marketing,analytics,data,conversation_intelligence,intent_abm,cdp,devops,security,customer_service,collaboration. Default = first 7 (B2B SaaS sales motion). - Custom universe (optional) —
["product_id_1", ...]to override curated default. - Use case (default
sales_prep) —sales_prep,battle_card,integration_partner_research,displacement_targeting. Affects play framing.
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 · 274 lines · 158 tokens per session scan A 717fb757f7eb
tech-stack-snapshot is a skill published in the GitHub repository Zoominfo/zoominfo-mcp-plugin (7 stars, last pushed yesterday), licensed MIT. It adds 158 tokens to every session and 3,705 once invoked, about $0.0008 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…
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…