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 repo-scopegit 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/repo-scope)<a href="https://agentmods.dev/skills/xzawed/claude-grok-build-plugin/repo-scope"><img src="https://agentmods.dev/badge/skills/xzawed/claude-grok-build-plugin/repo-scope/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/repo-scope"><img src="https://agentmods.dev/badge/skills/xzawed/claude-grok-build-plugin/repo-scope.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.00000 | $0.00755 |
| Opus 5 | $0.00000 | $0.00378 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
repo-scope 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo scope gate (claude-grok-build-plugin)
This repo's product scope is closed. docs/09-scope-and-residuals.md is the SSOT.
The rule
The default answer to "what's next?" is: nothing — unless docs/10-service-audit-queue.md
has open items, in which case the answer is "the top of that queue", and you say so plainly.
Do not open a PR the owner did not ask for. Unrequested "polish" is the failure this repo has already suffered repeatedly — a session looking for work invents it.
The queue is the exception, and only the queue. Its items were found by executing the shipped bundle and re-measuring each result independently (2026-09-05), so they are observed breakage, not invented work. Anything not in that queue still needs an owner goal first. Still ask before opening a PR — having a queue is not standing authorization to work through it.
Before answering "what's next"
- Read the
현재 상태block in rootCLAUDE.md, thendocs/10-service-audit-queue.md(open defects), thendocs/09-scope-and-residuals.md(scope). - Classify every residual before mentioning it. Never present an unclassified list:
| Class | Meaning | May you open a PR? |
|---|---|---|
| A — external | Consumer / orchestrator repo work | No. Doc pointer only |
| B — manual | Human + Claude Code GUI acceptance (docs/09 §5) |
No. It is a release ritual |
| C — deferred | ACP, pending a stated re-check trigger | No. Deferred ≠ next |
| D — excluded | Auto-commit, per-call authMode override | No. Out of scope by design |
| E — new feature | Only once the owner states a goal | Yes — after done criteria are written |
| F — measured defect | In docs/10-service-audit-queue.md — found by executing the shipped bundle |
Yes — after the owner picks it up. Not invented work |
- With no owner goal: if
docs/10-service-audit-queue.mdhas open items, the answer names the top one and stops there —docs/10 A<n> — 열린 결함 <count>건, 착수는 오너 승인 후. Only when that queue is empty is the answer이 레포 범위 완료 — 외부/수동/보류는 docs/09.
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.
- 3d ago Changed · +10 lines 82fd2f69f2f9
- 10d ago First seen · 44 lines · 0 tokens per session scan A c8e9061d86bc
repo-scope is a skill published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 755 tokens. 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
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
x-spec
A system-planning guide that turns a vague idea into a set of linked design documents. It defines goals, modules, interfaces, data, workflows, and ways to check the result.
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
learn
Explain recent vibe-learn session activity or answer a question about what was built, grounded in .vibe-learn/session-log.jsonl.
quiz
Check your understanding of the vibe-learn session — recall questions grounded in the session log, with results tracked across sessions in the knowledge ledger.