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 JordanGunn/nunchuck --skill grapegit clone --depth 1 https://github.com/JordanGunn/nunchuckWrote 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/jordangunn/nunchuck/grape)<a href="https://agentmods.dev/skills/jordangunn/nunchuck/grape"><img src="https://agentmods.dev/badge/skills/jordangunn/nunchuck/grape.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/jordangunn/nunchuck/grape"><img src="https://agentmods.dev/badge/skills/jordangunn/nunchuck/grape.svg?style=web" alt="Reviewed on agentmods" width="80" height="15"></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.00030 | $0.00185 |
| Opus 5 | $0.00015 | $0.00093 |
| Sonnet 5 | $0.00006 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
grape 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 8d 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
INSTRUCTIONS
- Refer to
metadata.references.
What ships with it
28 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.
- assets/examples/grape_compiled_plan_v1.example.json 944 B
- assets/examples/grape_surface_plan_v1.example.json 328 B
- assets/schemas/grape_compiled_plan_v1.schema.json 3.9 KB
- assets/schemas/grape_intent_v1.schema.json 1.8 KB
- assets/schemas/grape_surface_plan_v1.schema.json 1.8 KB
- assets/templates/grape_compiled_plan_v1.template.json 688 B
- assets/templates/grape_intent_v1.template.json 63 B
- assets/templates/grape_surface_plan_v1.template.json 303 B
- bootstrap.ps1 567 B runs code
- bootstrap.sh 455 B runs code
- README.md 2.9 KB
- references/00_ROUTER.md 487 B
- references/01_SUMMARY.md 840 B
- references/02_CONTRACTS.md 2.4 KB
- references/03_TRIGGERS.md 742 B
- references/04_NEVER.md 612 B
- references/05_ALWAYS.md 784 B
- references/06_PROCEDURE.md 855 B
- references/07_FAILURES.md 625 B
- scripts/grep.ps1 477 B runs code
- scripts/grep.sh 362 B runs code
- scripts/include/grape_cli.py 17 KB runs code
- scripts/plan.ps1 477 B runs code
- scripts/plan.sh 362 B runs code
- scripts/scan.ps1 477 B runs code
- scripts/scan.sh 362 B runs code
- scripts/skill.ps1 1.8 KB runs code
- scripts/skill.sh 1.4 KB runs code
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.
- 8d ago First seen · 33 lines · 30 tokens per session scan A 92549fbf2717
grape is a skill published in the GitHub repository JordanGunn/nunchuck (9 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 185 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
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.