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.
git clone --depth 1 https://github.com/VoidTechnology/voidtech-claude-pluginsWrote 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/plugins/voidtechnology/voidtech-claude-plugins/voidtech-engineering)<a href="https://agentmods.dev/plugins/voidtechnology/voidtech-claude-plugins/voidtech-engineering"><img src="https://agentmods.dev/badge/plugins/voidtechnology/voidtech-claude-plugins/voidtech-engineering/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/plugins/voidtechnology/voidtech-claude-plugins/voidtech-engineering"><img src="https://agentmods.dev/badge/plugins/voidtechnology/voidtech-claude-plugins/voidtech-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
voidtech-engineering 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
{
"name": "voidtech-engineering",
"version": "0.3.0",
"description": "VoidTech 工程工作流：架构、实现、调试、测试、Issue 与发布",
"author": {
"name": "VoidTech"
}
}
What it installs
The manifest is a name and a version. 14 skills, 1 agent travel with it, and installing the plugin installs all of them — 725 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill codebase-design A 50 tokens
- Skill prepare-issue A 37 tokens
- Skill ship A 51 tokens
- Skill setup-git-checks A 69 tokens
- Skill tdd A 37 tokens
- Skill feature-context A 44 tokens
- Skill debug A 44 tokens
- Skill architecture-review A 39 tokens
- Skill to-issues A 43 tokens
- Skill to-prd A 37 tokens
- Skill fix-conflicts A 27 tokens
- Skill implement A 20 tokens
- Skill git-safety B 61 tokens
- Skill logic-spike A 24 tokens
- Agent architect A 142 tokens
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 · 9 lines scan A 5142802af982
voidtech-engineering is a plugin published in the GitHub repository VoidTechnology/voidtech-claude-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
utility-tools
Developer productivity tools for Claude Code — generate McKinsey-style HTML slide decks from marketing strategies, automate software releases with version bumping, changelog generation, git tagging, and GitHub release publishing. 3 skills for teams shipping fast.
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
atlas-publish
Takes the open PRs of the Atlas/Bella monorepo to a registered draft release on either the over-the-air or the App Store lane, classifying between them from the expo-updates native fingerprint rather than from intent — ios.buildNumber sits inside that fingerprint, so a buildNumber bump alone forces a store release.…
oat-publish-python
Python release management: cleanup, version bump, uv build, GitHub release, publish monitoring.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.
essentials
Essential shipping workflow — group a dirty working tree into clean commits, push the branch, and open a senior-engineer-quality GitHub PR with auto-applied labels and "might address #X" issue links.