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/repo-checknpx skills add VoidTechnology/voidtech-claude-plugins --skill repo-checkgit 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.00029 | $0.00579 |
| Opus 5 | $0.00015 | $0.00290 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
repo-check 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 2d 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
仓库质量检查
用于 PR 前、发布前或怀疑文档与实现漂移时。只检查和报告；不得自动修改版本、放宽门禁、push、merge 或发布。
1. 确认范围
- 读取根
AGENTS.md和命中路径的专项规则。 - 运行
git status --short --branch，记录分支、worktree 和已有改动。 - 读取完整变更列表，按插件、根治理、CI、Renderer、Loop 分类。
2. 快速契约
node scripts/run-quality.mjs --tier contract
失败时报告具体事实源和漂移：README 数量或版本、失效链接、历史审计状态、未登记测试、插件未提升版本、缺少 CHANGELOG。
3. 风险触发验证
| 命中范围 | 追加命令 |
|---|---|
| 任意 Skill、Agent、Hook、MCP、manifest | node scripts/run-quality.mjs --tier portability |
| Product Runtime / schema | node scripts/run-quality.mjs --tier unit |
| Loop | node scripts/run-quality.mjs --tier unit，并请求 loop-security-reviewer |
| Renderer 输入或 harness | node scripts/run-quality.mjs --tier browser |
| Release | node scripts/run-quality.mjs --all 与 node scripts/run-quality.mjs --tier install-smoke |
不要把未命中平台或未执行命令写成已验证。
4. Review
需要内容 Review 时调用：
plugin-contract-reviewer：Skill、Agent、Hook、MCP、Marketplace、版本与可移植性。loop-security-reviewer：Loop 的 shell、Git、路径、状态、锁、审批和 eval 边界。
CI 通过不能替代 Review。
5. 输出
按以下顺序报告：
- 结论：可合入 / 不可合入 / 可发布 / 不可发布。
- P0/P1 问题：文件、行为、证据、修复条件；无则明确写“无”。
- 验证：实际命令和结果。
- 未验证与风险：平台、权限、外部服务和手工步骤。
- 下一步：唯一的具体动作。
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.
- 2d ago First seen · 56 lines · 29 tokens per session scan A dc4c40af7865
repo-check is a skill published in the GitHub repository VoidTechnology/voidtech-claude-plugins (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 29 tokens to every session and 579 once invoked, about $0.0001 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
new-changelog
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under packages/changelog/content. Use this when the task is specifically about determining the next version and creating the markdown entry.