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 Mburdo/knowledge_and_vibes --skill groundgit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWrote 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/mburdo/knowledge_and_vibes/ground)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/ground"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/ground/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/mburdo/knowledge_and_vibes/ground"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/ground.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.00047 | $0.02031 |
| Opus 5.5 | $0.00019 | $0.00812 |
| Sonnet 5.5 | $0.00009 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
ground 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 1mo 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ground — External Documentation
Verify external dependencies against current documentation before implementation. Direct execution.
Design rationale: This skill executes directly rather than spawning subagents because grounding is a simple query + verification sequence (~300 tokens), not substantial analytical work. Per Lita research: "Simple agents achieve 97% of complex system performance with 15x less code."
When This Applies
| Signal | Action |
|---|---|
About to write import for external lib |
Ground first |
| Using API/SDK methods | Verify current syntax |
| Framework-specific patterns | Check version compatibility |
| Auth/security code | Always verify current best practices |
| User says "ground" or "verify" | Run full grounding check |
| New library or major version | Deep grounding |
Default: When uncertain about external APIs, ground.
Tool Reference
Exa MCP Tools
| Tool | Purpose |
|---|---|
web_search_exa(query) |
General documentation search |
get_code_context_exa(query) |
Code examples from GitHub/tutorials |
crawling(url) |
Extract content from specific URLs |
Decision Tree
Where does truth live?
EXTERNAL DOCS ──► /ground (this skill)
"What's the current API for X?"
CODEBASE ───────► /explore (warp-grep)
"How does X work in our code?"
HISTORY ────────► /recall (cm + cass)
"How did we do this before?"
TASKS ──────────► bv --robot-*
"What should I work on?"
Execution Flow
Execute these steps directly. No subagents needed.
Step 1: Identify What Needs Grounding
Categories that need verification:
| Category | Why | Risk |
|---|---|---|
| Imports/Initialization | Syntax changes between versions | High |
| API Methods | Methods get renamed/deprecated | High |
| Configuration | Options/flags evolve | Medium |
| Async Patterns | Async APIs vary significantly | Medium |
| Auth/Security | Security best practices change | Critical |
| Data Validation | Validators/schemas evolve | Medium |
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.
- 1mo ago First seen · 326 lines · 47 tokens per session scan A 7505c3637506
ground is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 9mo ago), licensed MIT. It adds 47 tokens to every session and 2,031 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…