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/choiyounggi/groundwork/setupnpx skills add choiyounggi/groundwork --skill setupgit clone --depth 1 https://github.com/choiyounggi/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.00031 | $0.00782 |
| Opus 5 | $0.00015 | $0.00391 |
| Sonnet 5 | $0.00006 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
setup 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 yesterday.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
memory-loop: setup
Walk the user through first-time setup, in this order. Every step is optional — respect a "skip".
1. Identity
Run the identity skill flow: offer the one-time name setup (set or decline).
See that skill for the schema and the confirmation rule.
2. HABITS.md
The habit-distillation frame is two files — rules that load every session, and the case records they point to, which do not:
~/.claude/groundwork/HABITS.md (imported into every session)
~/.claude/groundwork/HABITS-CASES.md (on demand, via [Cnn] pointers)
- If they do not exist, copy the templates:
mkdir -p ~/.claude/groundwork cp "${CLAUDE_PLUGIN_ROOT}/templates/HABITS.md" ~/.claude/groundwork/HABITS.md cp "${CLAUDE_PLUGIN_ROOT}/templates/HABITS-CASES.md" ~/.claude/groundwork/HABITS-CASES.md - If either already exists, never overwrite it — it holds the user's
accumulated habits. Because of that, re-running this step is also the
migration path for a HABITS.md that predates the two-file layout: the cases
file gets created, the habit file is left exactly as it is. (The
habitskill describes how to move the prose across.) - Then suggest (do not apply) adding an import line to the user's own
~/.claude/CLAUDE.mdso the habits load into every session — show them the exact line and let them add it:
(The path is relative to@groundwork/HABITS.md~/.claude/. Never edit the user's CLAUDE.md yourself.) Import only HABITS.md — HABITS-CASES.md is deliberately left out so its prose is not re-read on every request.
3. Config
Offer to copy the example config to the global location:
cp "${CLAUDE_PLUGIN_ROOT}/examples/memory-loop.example.json" ~/.claude/groundwork/memory-loop.json
Explain the two keys before copying:
nudgeInterval— the learning-review nudge fires every N responses (default 10; raise it for less frequent reviews).extraMemoryDirs— additional memory directories the expiry sweep should cover, beyond the current project's own memory directory.
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.
- yesterday First seen · 80 lines · 31 tokens per session scan A 8c4e4b98ee9d
setup is a skill published in the GitHub repository choiyounggi/groundwork (3 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 782 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-08-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
ideal-customer-profile
Identify the Ideal Customer Profile (ICP) from research data with demographics, behaviors, JTBD, and needs. Use when defining your ICP, analyzing PMF survey data, or understanding who your best customers are.