Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add RadOrigin-LLC/RAD-Claude-Skills/plugin install rad-explainWrote 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/radorigin-llc/rad-claude-skills/ground-readme)<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/ground-readme"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/ground-readme/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/radorigin-llc/rad-claude-skills/ground-readme"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/ground-readme.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.00148 | $0.02210 |
| Opus 5 | $0.00074 | $0.01105 |
| Sonnet 5 | $0.00030 | $0.00442 |
| Haiku 4.5 | $0.00015 | $0.00221 |
Grade A, and why
ground-readme 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ground README — Audit or generate honest project listings
You are either auditing an existing README/marketplace listing for overpromise and unbacked claims, or generating a new one from actual code with grounding controls.
This is the README-shaped version of the rad-explain principle: every substantive claim in a project's outward-facing copy should be checkable against source, and nothing should use marketing/sensational language. The principle is the same one the rad-claude-skills marketplace applied to its own listings post-audit.
Foundational rules
- Grounded. Every claim about what the project does must trace to code, docs, or test evidence. The
check-grounding.pyvalidator runs against the output. - Not overpromising. No "the only" / "world-class" / "revolutionary" / "production-grade" without evidence. The
check-overpromise.pyvalidator runs against the output.
These are non-negotiable. If they fail, the skill surfaces findings and offers revision before finalizing.
Modes
audit (most common)
Review an existing README, marketplace listing, plugin.json description, or similar outward-facing copy. Produce a findings report.
Workflow:
- Read the target file (default:
README.mdat repo root) - Run
check-overpromise.pyagainst it - Run
check-grounding.pyagainst the repo - Read the actual code/docs to verify capability claims
- Surface findings with line numbers + suggested rewrites
- Optionally write a revised version
Output: a findings report (Markdown) listing:
| Section | What was flagged |
|---|---|
| Overpromise findings | Each flagged phrase with line number, severity, and a suggested concrete replacement |
| Unbacked claims | Each claim with no traceable source, with suggested either: remove, add source, or rephrase |
| Capability mismatches | Claims that traced to source but the source DOESN'T support the claim (e.g., README says "supports MongoDB" and there's no MongoDB code) |
| Missing claims | Things the code actually does that the README doesn't mention (the inverse — under-promising) |
| Suggested rewrites | For high-severity findings, a concrete replacement sentence |
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 · 228 lines · 148 tokens per session scan A f58fd3bbadb7
ground-readme is a skill published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 25d ago), licensed Apache-2.0. It adds 148 tokens to every session and 2,210 once invoked, about $0.0007 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
bug-reporting
Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and…
audio-video
Load this skill whenever the project contains audio or video content, media players, podcasts, video embeds, or any / elements. Under no circumstances publish audio or video without captions, transcripts, and audio descriptions where required. Absolutely always apply WCAG 1.2 criteria for time-based media.
charts-graphs
Load this skill whenever the project contains charts, graphs, data visualizations, infographics, or any visual representation of data (bar charts, line charts, pie charts, scatter plots, dashboards). Under no circumstances render a chart without a text alternative, data table, or summary. Prioritize conveying the same…
light-dark-mode
Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level…
maps
Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are…
mermaid
Load this skill whenever the project uses Mermaid diagrams — flowcharts, sequence diagrams, class diagrams, Gantt charts, or any Mermaid-rendered visualization. Under no circumstances render a Mermaid diagram without an accessible title, description, and text-based alternative. Absolutely always add accTitle: and…