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/hbui290/voz-knowledge-mcp/voz-knowledgenpx skills add hbui290/voz-knowledge-mcp --skill voz-knowledgegit clone --depth 1 https://github.com/hbui290/voz-knowledge-mcpWrote 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/hbui290/voz-knowledge-mcp/voz-knowledge)<a href="https://agentmods.dev/skills/hbui290/voz-knowledge-mcp/voz-knowledge"><img src="https://agentmods.dev/badge/skills/hbui290/voz-knowledge-mcp/voz-knowledge.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.1 | $0.00084 | $0.01618 |
| Opus 5 | $0.00042 | $0.00809 |
| Sonnet 5 | $0.00017 | $0.00324 |
| Haiku 4.5 | $0.00008 | $0.00162 |
Grade A, and why
voz-knowledge 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VOZ Knowledge
Overview
Use the local voz_knowledge_mcp server as the source of truth for VOZ thread collection. Prefer MCP tools over ad hoc browsing when the user wants reusable archive/search/summarization, not just a one-off glance.
Tool Workflow
Use these MCP tools when available:
read_thread(url, mode="auto", max_pages=None): archive a VOZ thread and return structured posts/assets.summarize_thread(url, mode="auto"): archive the thread and create a Markdown summary underreports/voz/summaries/.search_archive(query, limit=50): quick keyword lookup in archived posts; not enough for full-thread insight synthesis.search_archive_grouped(query, limit_per_group=5, max_matches=500): keyword lookup grouped by heuristic topic.extract_links(url, mode="auto"): archive the thread and return links/images/assets.crawl_threads(urls, mode="auto", max_pages=None): archive several threads.build_thread_packet(url, mode="auto", max_posts=None): archive and build a clean full-thread packet for insight synthesis; writes the full packet toarchive/packets/.topic_digest(url, topic, mode="auto", max_posts=200): digest one topic from the full thread instead of relying on search limits.setup_browser_cdp(): launch installed Chromium-family browsers with local CDP ports for browser fallback.
If the MCP tools are not exposed in the current environment, use the local CLI from the MCP project root:
python -m voz_knowledge_mcp.cli read-thread "<VOZ_URL>" --mode auto
Knowledge Workflow
When the user asks to "cao noi dung", "tong hop kien thuc", "rut insight", "viet thanh bai chia se", or anything beyond a brief summary, do not stop at summarize_thread. Use this workflow:
- Archive the thread with
read_threadorsummarize_threadinmode="auto". - Call
build_thread_packetfor whole-thread insight work, ortopic_digestfor one topic. Do not base insight onsearch_archivealone. - Remove obvious noise posts such as bumps, thanks-only replies, bookmarks, app signatures, empty replies, and jokes that add no knowledge.
- Clean links carefully:
- Remove forum mechanics:
voz.vn/goto/post?id=..., quote/share links, profile links, app signature links, smilies, emoji CDN,data:imageplaceholders. - Preserve real resources: VOZ attachments, VOZ thread/post links, YouTube, Reddit, Facebook, TikTok, X/Twitter, Telegram, tool pages, files, and other external URLs.
- Remove forum mechanics:
- Inspect preserved content links before writing insight:
- Read VOZ thread/post links when accessible.
- Open Reddit/YouTube/Facebook/TikTok/tool links when accessible; summarize their role in the discussion.
- If a dynamic site cannot be fully inspected, say what was accessible and avoid inventing details.
- Treat images/screenshots as evidence, not standalone content:
- Link them beside the source post they support.
- Summarize only what is visible or what the surrounding posts explain.
- Write a natural insight guide, not a mechanical report. Read
references/insight-writing.mdbefore producing long-form knowledge artifacts.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 106 lines · 84 tokens per session scan A 765ff35c0252
voz-knowledge is a skill published in the GitHub repository hbui290/voz-knowledge-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 1,618 once invoked, about $0.0004 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.
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…
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…
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…