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/voidtechnology/voidtech-claude-plugins/feature-contextnpx skills add VoidTechnology/voidtech-claude-plugins --skill feature-contextgit clone --depth 1 https://github.com/VoidTechnology/voidtech-claude-pluginsWhat 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.00044 | $0.00867 |
| Opus 5 | $0.00022 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00087 |
Grade A, and why
feature-context 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.
What it actually says
Vendored from mattpocock/skills · MIT © 2026 Matt Pocock · upstream 6eeb81b · 已汉化并完成 VoidTech 插件内自包含适配。LICENSE 见 ../_vendor-licenses/mattpocock-LICENSE
功能上下文
在设计过程中同步维护项目的功能上下文：检查业务词汇是否准确，用具体场景验证概念边界，并把确认后的术语和决策及时写入词汇表或 ADR。仅仅读取 CONTEXT.md 不需要调用本技能；只有新增、修改或澄清功能上下文时才使用。
文件结构
多数仓库只有单一上下文：
/
├── CONTEXT.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
如果根目录存在 CONTEXT-MAP.md，说明仓库有多个上下文。这张图指向每个上下文所在之处：
/
├── CONTEXT-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── CONTEXT.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── CONTEXT.md
│ └── docs/adr/
按需创建文件。确认第一个业务术语时再创建 CONTEXT.md；需要记录第一份 ADR 时再创建 docs/adr/。
会话进行中
对照词汇表检查用词
当用户用的术语与 CONTEXT.md 中既有的语言冲突时，立即指出。"你的词汇表把 'cancellation' 定义为 X，但你似乎指的是 Y——到底是哪个？"
明确含糊的措辞
当用户使用模糊或一词多义的术语时，提出一个精确的规范术语。"你说 'account'——你指的是 Customer 还是 User？这是两样不同的东西。"
用具体场景验证
讨论业务概念关系时，使用具体场景验证边界情况，帮助用户明确相近概念之间的区别。
与代码交叉核对
当用户说明某项业务规则时，检查代码是否一致。发现矛盾时直接指出："代码会取消整个 Order，但你刚才说可以部分取消。哪一个才是预期行为？"
内联更新 CONTEXT.md
术语确认后立即更新 CONTEXT.md，不要等到会话结束再集中整理。使用 CONTEXT-FORMAT.md 中的格式。
CONTEXT.md 应当完全不含实现细节。不要把 CONTEXT.md 当成规格、草稿本或实现决策的仓库。它是一份词汇表，仅此而已。
谨慎提议 ADR
只有当以下三点同时成立时，才提议创建 ADR：
- 难以逆转 — 以后改变决定的成本较高
- 缺少背景就难以理解 — 未来读者可能无法判断为什么这样选择
- 是一次真实权衡的结果 — 确有可选项，而你为了特定理由选了其一
只要三者缺一，就跳过 ADR。使用 ADR-FORMAT.md 中的格式。
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.
- yesterday First seen · 76 lines · 44 tokens per session scan A 4b2a1bb76237
feature-context is a skill published in the GitHub repository VoidTechnology/voidtech-claude-plugins (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 44 tokens to every session and 867 once invoked, about $0.0002 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…