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 vasilyu1983/AI-Agents-public --skill foundations-grounding-communicationgit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/foundations-grounding-communication)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/foundations-grounding-communication"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-grounding-communication/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/vasilyu1983/ai-agents-public/foundations-grounding-communication"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-grounding-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.07449 |
| Opus 5 | $0.00018 | $0.03725 |
| Sonnet 5 | $0.00007 | $0.01490 |
| Haiku 4.5 | $0.00004 | $0.00745 |
Grade A, and why
foundations-grounding-communication 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.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grounding & Communication Foundations
Scope note — two senses of "grounding": This skill covers the Clark conversational sense: establishing shared meaning between parties (common ground, acceptance evidence, repair). It does not cover the LLM-attribution / RAG sense: whether a generated response is grounded in retrieved documents (citation faithfulness, hallucination detection). For the attribution sense, see ai-rag and the FACTS Grounding / RAGAS / Wallat et al. frameworks (sources FACTSGrounding2025, RAGAS2024, WallatFaithfulness2024 in data/sources.json).
10 canonical grounding-theory primitives for the process by which two or more parties establish enough shared understanding to coordinate. Founded by Herbert Clark and colleagues (1989, 1991, 1996), grounding theory is the most-cited formal account of how interlocutors solve the "do we mean the same thing?" problem efficiently.
It is the missing layer for multi-agent LLM systems: empirical work on multi-agent failures (MAST taxonomy, NeurIPS 2025) identifies system-design specification issues, inter-agent misalignment, and task-verification gaps across 1,600+ traces. Agents often proceed on different interpretations of the same brief. That is not only a coordination problem (information structure); it is a grounding problem (insufficient common ground at handoff). foundations-team-theory tells you whether agents should communicate; this skill tells you how they actually establish shared meaning when they do.
Static vs. dynamic grounding (2026). The distinction now carries the most diagnostic weight. Static grounding maps language to a shared context in one shot; dynamic grounding requires negotiating meaning across turns — joint plan formation, commitment, and execution. Yao, Zou, and Hawkins (2026) show the gap is not a reasoning-capacity problem: in an iterated negotiation game with verifiable jointly optimal outcomes, agents that identify Pareto-optimal allocations in isolation consistently fail to reach them as dyads, across models. Their four failure modes — loss of shared interaction history, anchoring to early proposals, defaulting to equal splits over reward-maximizing coordination, and referential binding errors across turns — map onto primitives #1, #3, #8, and #6 respectively. Most benchmarks and most agent handoff designs still test only the static case.
What ships with it
7 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.
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 · 311 lines · 37 tokens per session scan A 2a0cac65353c
foundations-grounding-communication is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 9d ago), licensed MIT. It adds 37 tokens to every session and 7,449 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-09-03.
Other skills, from other repositories
eli5
Explain a topic like I'm a 5 year old — restate my last output, or a named topic, in plain words without dropping a single fact. Use when the user types /eli5 [topic], or says an answer was too technical, too long, or unclear about what he now has to do.
read-papers
Finds the latest research papers on a specific topic, summarizes their core contributions, and explains complex methodology in plain English.
summarize-podcast
Extracts transcripts from podcasts or videos and synthesizes actionable takeaways.
code-walkthrough
Use when guiding a developer through unfamiliar codebases via step-by-step walkthroughs.
aetox-teach
สอนคนใช้ Aetox — ทำอะไรได้บ้างในคำที่คนเข้าใจ ห้องไหนไว้ทำอะไร ห้าอย่างที่คนใหม่ต้องรู้ และวิธีสอนด้วยการลงมือทำงานจริงของเขาแทนการบรรยาย · อ่านเมื่อผู้ใช้ถามว่าแอปนี้ทำอะไรได้ ถามวิธีใช้ หรือเพิ่งเปิดครั้งแรก.
teach
Explain a body of work plainly so a person actually understands it. Runs the how and why skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.