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 agentmods add skills/etr/groundwork/groundwork-checknpx skills add etr/groundwork --skill groundwork-checkgit clone --depth 1 https://github.com/etr/groundworkWhat 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 | $0.00021 | $0.00313 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade B, and why
groundwork-check scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Missing execute permission | Run `chmod 755` on script | What it actually says
Groundwork Plugin Health Check
Validates the Groundwork plugin installation and reports any issues.
Workflow
Step 1: Run Validation Script
Run the plugin validation script:
node "${CLAUDE_PLUGIN_ROOT}/lib/validate-plugin.js"
Step 2: Report Results
Present the validation results to the user:
- If all checks pass: Confirm plugin is healthy
- If errors found: List each error with file path and description
- If warnings found: List warnings as recommendations
Step 3: Suggest Fixes
For any issues found, suggest specific fixes:
| Issue Type | Suggested Fix |
|---|---|
| Missing frontmatter | Add --- delimited YAML at file start |
Literal \n in description |
Use YAML block scalar (|) |
| Non-standard field | Remove field or document exception |
| allowed_tools | Change to allowed-tools (hyphen) |
| @ syntax | Use explicit file paths |
| Missing execute permission | Run chmod 755 on script |
Step 4: Offer to Fix
If issues are found, offer to automatically fix simple issues:
- Permissions can be fixed with chmod
- YAML key names can be updated
Ask user before making any changes.
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.
- 2d ago First seen · 50 lines · 21 tokens per session scan B 41473efbac77
groundwork-check is a skill published in the GitHub repository etr/groundwork (42 stars, last pushed 21d ago), licensed MIT. It adds 21 tokens to every session and 313 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.