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 skills add xzawed/claude-grok-build-plugin --skill maintainer-preflightgit clone --depth 1 https://github.com/xzawed/claude-grok-build-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/xzawed/claude-grok-build-plugin/maintainer-preflight)<a href="https://agentmods.dev/skills/xzawed/claude-grok-build-plugin/maintainer-preflight"><img src="https://agentmods.dev/badge/skills/xzawed/claude-grok-build-plugin/maintainer-preflight/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/skills/xzawed/claude-grok-build-plugin/maintainer-preflight"><img src="https://agentmods.dev/badge/skills/xzawed/claude-grok-build-plugin/maintainer-preflight.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01935 |
| Opus 5.5 | $0.00024 | $0.00774 |
| Sonnet 5.5 | $0.00012 | $0.00387 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
maintainer-preflight 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 17d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer preflight (claude-grok-build-plugin)
Run these before saying done. Evidence, not vibes.
And these gates are not the last step. Step 8 of "작업 수행 방법" in root CLAUDE.md —
post-execution verification plus an audit of the measurements that got you here — is mandatory
and runs AFTER the PR merges. CLAUDE.md owns that rule; do not restate it here. The short of
it: check origin/main content rather than the log, re-run the original reproduction against
the shipped bundle, and re-derive every finding by a second independent method before acting on
it. Measured 2026-09-12: in one audit the measurement harness was wrong 6 times against 2 real
defects.
A code fix also needs a Grok second opinion before done — the adversarial pass is step 5 of
"작업 수행 방법" in root CLAUDE.md; the full recipe and its history live in
docs/11-maintainer-playbook.md "5번 조리법" (its old rationale — "a prose-only review prompt never
terminates" — did not reproduce on 2026-09-12; use the recipe, do not cite that as a law). Give Grok
the code verbatim, not retyped facts. Read its verdict.md yourself, and verify any finding by
measurement before acting on it.
Always
cd mcp-server
npm ci # missing OR possibly-stale node_modules — see below
npm test
npm run typecheck
Both must pass. Report the real counts from this session's run — never summarize a run you did not execute.
npm ci is not only for a missing node_modules. A tree that is merely stale is worse
than a missing one, because the build succeeds and silently ships the wrong dependency. Measured
2026-08-09: node_modules held fast-uri 3.1.4 while the lockfile pinned 3.1.5, and
npm run build produced a dist/index.js with the v0.2.6 security patch (GHSA-7p8r-x3mc-p8w7)
removed — a clean-looking rebuild that reverted a shipped fix. Cheap check before trusting a
build:
node -e "console.log(require('./node_modules/<pkg>/package.json').version)" # vs package-lock.json
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.
- 17d ago Changed · -4 lines a5751e579b7a
- 22d ago Changed · +2 lines e51c374ec028
- 28d ago Changed · +2 lines 9715856b8375
- 1mo ago Changed · +8 lines 61bf8251c69a
- 1mo ago Changed · +5 lines bf4fbe70c553
- 1mo ago Changed · +8 lines 0b1561377665
- 1mo ago First seen · 123 lines · 61 tokens per session scan A d448fa006fe3
maintainer-preflight is a skill published in the GitHub repository xzawed/claude-grok-build-plugin (3 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,935 once invoked, about $0.0002 per session on Opus 5.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
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
mock-detection
Deep mock appropriateness analysis for Test Audit pipeline.
bug-magnet-data
Curated edge case test data for boundary testing, verification scripts, and test generation. Provides pre-curated reference data organized by data type with context-specific loading guidance.
assertion-patterns
Real output verification vs mock calls. Use when transforming T1-T4 violating tests to verify observable behavior.
test-classification
Prompt template for test classification stage in Test Audit pipeline.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.