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 IamK77/Skill --skill groundworkgit clone --depth 1 https://github.com/IamK77/SkillWrote 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/iamk77/skill/groundwork)<a href="https://agentmods.dev/skills/iamk77/skill/groundwork"><img src="https://agentmods.dev/badge/skills/iamk77/skill/groundwork/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/iamk77/skill/groundwork"><img src="https://agentmods.dev/badge/skills/iamk77/skill/groundwork.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.00029 | $0.01004 |
| Opus 5.5 | $0.00012 | $0.00402 |
| Sonnet 5.5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00100 |
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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groundwork
Turn a request into an agreed, testable task definition. Use when requirements, constraints, examples, or acceptance boundaries are unclear.
Inputs
The human’s request; affected users and current behaviour; known constraints; who can resolve conflicting requirements.
Run record
Use checklist 0.5 or newer for this SOP. Reading or reloading the skill must not reset work. For a new task, run checklist init "${CLAUDE_SKILL_DIR}" --new --path "/absolute/project"; retain its returned ID as RUN. For existing work, use checklist resume "$RUN", then checklist show --run "$RUN". Outside Claude, replace the skill-directory variable with this directory’s actual path.
Commands below record work after it is done. Replace evidence placeholders with concise artifact locations and observations. Manual confirmations are not independent proof; a sensor pass covers only the command and inputs it observed. verify does not close a stage; advance checks that its required readings are fulfilled. Use report --run "$RUN" for the retained history.
Procedure
understand
Restate the desired outcome and ask only the questions that change scope or acceptance. Separate facts, assumptions, and choices still owned by the human.
Record these artifacts after doing the work:
- Users, problem, and desired outcome are stated.
checklist check understand need --run "$RUN" --evidence "<artifact and observation>" - Material ambiguities and their decision owners are recorded.
checklist check understand unknowns --run "$RUN" --evidence "<artifact and observation>"
When this stage is fulfilled: checklist advance understand --run "$RUN".
specify
Write concrete success and failure examples, non-goals, constraints, and interfaces affected. Resolve contradictions with the decision owner rather than selecting a requirement silently.
What ships with it
9 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.
- 1mo ago Changed · -51 lines · -101 tokens per session 653cdc255bbd
- 2mo ago First seen · 142 lines · 130 tokens per session scan A 6bb7ab6c0921
groundwork is a skill published in the GitHub repository IamK77/Skill (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,004 once invoked, about $0.0001 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-31.
groundwork compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| groundworkIamK77/Skill | Skill | 2 | 1mo ago | Apache-2.0 | A | 29 | Claude Code |
| agents-v2-pylingxling/awesome-skills-cn | Skill | 334 | 1mo ago | MIT | A | 39 | Claude Code |
| analytics-productlingxling/awesome-skills-cn | Skill | 334 | 1mo ago | MIT | A | 35 | Claude Code |
| api-security-best-practiceslingxling/awesome-skills-cn | Skill | 334 | 1mo ago | MIT | A | 29 | Claude Code |
| antigravity-workflowslingxling/awesome-skills-cn | Skill | 334 | 1mo ago | MIT | A | 41 | Claude Code |
| apex-skillifytonone-ai/tonone | Skill | 77 | 4d ago | MIT | A | 41 | Claude Code |
| oci-services-expertfrankxai/claude-skills-library | Skill | 47 | yesterday | MIT | A | 43 | Claude Code |