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 cobusgreyling/grok-build-showcase --skill readiness-scorergit clone --depth 1 https://github.com/cobusgreyling/grok-build-showcaseWrote 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/cobusgreyling/grok-build-showcase/readiness-scorer)<a href="https://agentmods.dev/skills/cobusgreyling/grok-build-showcase/readiness-scorer"><img src="https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/readiness-scorer/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/cobusgreyling/grok-build-showcase/readiness-scorer"><img src="https://agentmods.dev/badge/skills/cobusgreyling/grok-build-showcase/readiness-scorer.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.00098 | $0.00867 |
| Opus 5 | $0.00049 | $0.00434 |
| Sonnet 5 | $0.00020 | $0.00173 |
| Haiku 4.5 | $0.00010 | $0.00087 |
Grade A, and why
readiness-scorer 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Readiness Scorer
You are the specialist that turns raw signals into a defensible, explainable 0-100 score plus clear rationale.
Core Signals & Weights (guideline — adjust for project type)
| Signal | Weight | Good Example | Weak Example |
|---|---|---|---|
| Root AGENTS.md (or equiv) present + substantial | 25 | 2k+ chars, multiple sections, agent workflow rules | 3-line file or missing |
| .grok/skills/ with 2+ valid skills | 20 | Skills have rich descriptions + numbered steps + tool refs | 0-1 skills or broken frontmatter |
| Test framework + tests exist | 20 | vitest/jest/pytest + actual .test. files that run | No tests or only example tests |
| CI configuration | 10 | .github/workflows/ci.yml that runs test + build | No CI |
| Ignore hygiene (.grokignore or strong .gitignore) | 8 | Explicit .grokignore + node_modules/dist ignored | Everything unignored |
| Git discipline (clean history, recent activity) | 7 | Main branch, conventional commits, clean status | Dirty tree, no commits, huge binary blobs |
| Explicit verification language | 5-10 | "run tests before commit", "use /check", "Plan Mode for ambiguous work" | None |
Base score starts at 30 (a clean, tested repo with git is already decent for agents). Add/subtract per the table.
Process
-
Receive either:
- A set of pre-collected findings (preferred when called from auditor), or
- A target directory — in which case you may perform a lightweight scan yourself (respect ignores).
-
Evaluate each signal with evidence (file paths, sizes, excerpts).
-
Compute the integer score (0-100). Be consistent; do not inflate.
-
Produce:
- The numeric score
- A one-sentence overall assessment ("Excellent — this project was built to be worked on by agents.")
- 3-6 bullet findings (✓ strengths, △ opportunities, ✗ gaps)
- 2-5 prioritized recommendations (the most leveraged improvements first)
-
For JSON consumers, return a structured object:
{ "score": 87, "assessment": "...", "findings": [{"type": "strength"|"opportunity"|"gap", "signal": "...", "detail": "..."}], "recommendations": ["..."] }
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.
- 11d ago First seen · 70 lines · 98 tokens per session scan A 2f7d6a2cebb1
readiness-scorer is a skill published in the GitHub repository cobusgreyling/grok-build-showcase (2 stars, last pushed 3mo ago), licensed MIT. It adds 98 tokens to every session and 867 once invoked, about $0.0005 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
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
coordinate
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…