groundwork

groundwork is a skill for Claude Code, Codex from samsantosb/ship-it. It costs 41 tokens per session (2,481 once invoked), scanned A, original, MIT.

A one-time project setup skill for a development workflow. It detects the project's task tracker, code repository, reviewer, notification method, and validation tools, then saves that configuration.

In plain words
What is it for?
Use it when starting the workflow in a project or changing its setup. It prepares the configuration used by the other development skills.
Why use it?
It prevents later workflow steps from repeatedly asking where work should be tracked, how code is reviewed, or who should be notified. Re-running it updates the existing setup.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the ship-it plugin — 7 skills shipped together

Install

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.

agentmods
npx agentmods add skills/samsantosb/ship-it/groundwork
Any agent
npx skills add samsantosb/ship-it --skill groundwork
Clone the repo
git clone --depth 1 https://github.com/samsantosb/ship-it

Made for: Claude Code, Codex.

Or install ship-it, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for groundwork

README.md
[![agentmods](https://agentmods.dev/badge/skills/samsantosb/ship-it/groundwork.svg)](https://agentmods.dev/skills/samsantosb/ship-it/groundwork)
Your own site
<a href="https://agentmods.dev/skills/samsantosb/ship-it/groundwork"><img src="https://agentmods.dev/badge/skills/samsantosb/ship-it/groundwork.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,481 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.02481
Opus 5 $0.00020 $0.01241
Sonnet 5 $0.00008 $0.00496
Haiku 4.5 $0.00004 $0.00248

Measured 5d ago against content hash 5cfe6e627cc3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

groundwork 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 5d 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.

skills/groundwork/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: groundwork

Lays the groundwork every other skill stands on: the per-project configuration (${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md). Runs once per project; rerunning updates the existing config instead of duplicating it. groundwork writes config as its job — the "offer to persist" write-back protocol governs the other skills when they resolve roles ad hoc. Respond in the conversation language (docs/agents/language.md; not yet configured → mirror the user's language).

Load before acting: ${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md (the config this skill writes) and ${CLAUDE_PLUGIN_ROOT}/shared/guardrails.md — this skill writes project files; the loading contract applies.

Process

1 — Detect (silent, no questions yet)

Run the capability detection from ${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md for all four roles plus validation:

  • Tracker: tracker MCPs by capability signature (never by server prefix); git remote -v; gh auth status / glab auth status; existing tasks/ directory.
  • Repo: git rev-parse --show-toplevel; remote host; base branch — gh repo view --json defaultBranchRef -q .defaultBranchRef.name, falling back to git symbolic-ref refs/remotes/origin/HEAD, then git ls-remote --symref origin HEAD, then assume main. If the assumed base doesn't exist locally either (fresh git init), record the current local branch instead and flag the mismatch in tracker.md and the handoff.
  • Reviewer: .coderabbit.yaml present, or gh pr list --search "reviewed-by:coderabbitai" --state all --limit 5 returning results (swap the login to probe other known bots). Treat a failed command and an empty result the same — both mean "no bot detected" (gh subcommands are inconsistent here: some exit 1, some exit 0 with empty output). Detected bot → watch: on by default; otherwise self-review, no watch.
  • Notifier: notifier MCPs by capability signature; otherwise chat.
  • Validation: package.json scripts — root and per workspace (monorepo signals: workspaces field, pnpm-workspace.yaml, turbo.json; workspaces declared but empty → record root commands and note it). Makefile; commands declared in CLAUDE.md/AGENTS.md. PR size budget: grep guideline files (CLAUDE.md, GUIDELINES.md, CONTRIBUTING.md) for a declared max-PR-size rule; not found → this is always asked in step 2 (recommended option: "500 changed production lines") — never silently omitted.
  • Labels: gh label list (or tracker equivalent); scan .github/workflows/*.yml for jobs that fail on missing labels — those labels become the required set in labels.md.
  • Observability: dependencies and config files (newrelic, datadog, @sentry/*, prom-client, OpenTelemetry SDKs, winston/pino); dashboards-as-code in infra/; guideline files. Not detected → leave for lazy resolution (create-tasks asks the first time a card needs it).
  • Guardrails (Layer 2): guideline files (CLAUDE.md, AGENTS.md, GUIDELINES.md, CONTRIBUTING.md) for stated conventions; generated-code markers ("do not edit" headers, codegen output dirs) → propose protected entries.
  • Language: the language the user has been writing in this session — becomes the recommended answer for the conversation-language question in step 2; never silently assumed into config.

Read the full file on GitHub · 126 lines

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.

  1. 5d ago First seen · 126 lines · 41 tokens per session scan A 5cfe6e627cc3

Subscribe to this mod's changes

groundwork is a skill published in the GitHub repository samsantosb/ship-it (23 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,481 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens