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 ikenga-hq/ikenga-pkgs --skill groundworkgit clone --depth 1 https://github.com/ikenga-hq/ikenga-pkgsWrote 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/ikenga-hq/ikenga-pkgs/groundwork)<a href="https://agentmods.dev/skills/ikenga-hq/ikenga-pkgs/groundwork"><img src="https://agentmods.dev/badge/skills/ikenga-hq/ikenga-pkgs/groundwork.svg" alt="Measured on agentmods" 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.00416 | $0.05798 |
| Opus 5 | $0.00208 | $0.02899 |
| Sonnet 5 | $0.00083 | $0.01160 |
| Haiku 4.5 | $0.00042 | $0.00580 |
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 7d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groundwork — research → plan → orchestrate → act, packaged
This file is a router. Each action and each agent role lives in its own file under actions/ and agents/; load on demand. The state mechanism (.groundwork.json, fences, hash-diff, IDs) is fully specified in lib/state.md — every action obeys it. Read lib/state.md before doing anything that writes to disk.
The full design lives in plans/groundwork/01-plan.md; locked decisions in plans/groundwork/04-discussion.md (Rounds 1–4). This skill is the executable form of that plan.
What groundwork is for
Stripped to one sentence: a stateless action-set that scaffolds and maintains a folder of living planning documents, with traceable IDs threading plan → tracking → orchestration → board, so re-runs augment instead of clobber and a multi-agent kickoff falls out the back end. Originated from the com.ikenga.studio planning workflow; generalized so it works for non-code, non-Ikenga work too.
Surface model:
| Surface | What it is | Trigger |
|---|---|---|
Scaffolder (init) |
First-run interview + folder skeleton drop | User has a goal but no plan folder |
Action: research |
Researcher agent fills 02/03 |
After scaffolder, or to refresh |
Action: design |
Produces ≥2 comparable designs/*.html for the current phase, locks one |
Visual/UX work, profile-gated |
Action: subplan |
Scaffolds a focused NN-*.md from one of three archetypes (diff-plan / decision-doc / bug-doc) |
A hard piece needs its own focused doc (critical-path PR plan, between-round deliberation, postmortem) |
Action: review |
Reviewer agent → new Round in 04 → re-sync via IDs |
Recurring, highest-value |
Action: clarify |
Readiness gate before orchestrate |
Before kickoff |
Action: orchestrate |
Generates 09-orchestration.md from 05 |
When ready to kick off |
Action: refresh-board |
(Re)generates artifact/board.html & artifact/explorer.html and opens/returns artifact/explorer.html |
Whenever board falls behind |
Action: refresh-living-spec |
Regenerates the spec-state fence inside artifact/index.html (Phasing/Decisions/Risks tabs) from .groundwork.json + 04 + 05 + 01 §Risks |
When the living-spec's auto tabs fall behind |
Action: explorer |
(Re)generates artifact/explorer.html — a file-tree + tabbed viewer (with search) of the whole plan folder; sibling to the board (opens it as a tab) |
Browse the plan's files as one navigable view |
Action: plans-index |
(Re)generates <plans-dir>/_index.html — a cross-plan dashboard: one card per plan with status rollups + drill-in to each plan's explorer/board |
See every plan in a project at once |
Action: issue-sync |
Provisions & syncs native Git forge issues (GitHub/GitLab) for WP-NNs |
Remote status tracking & PR integration |
Action: status |
Read-only freshness + ID + design-coverage + sub-plan report | Anytime |
What ships with it
60 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.
- .gitattributes 19 B
- actions/clarify.md 6.5 KB
- actions/design.md 21 KB
- actions/explorer.md 14 KB
- actions/init.md 13 KB
- actions/issues.md 5.6 KB
- actions/orchestrate.md 15 KB
- actions/plans-index.md 7.6 KB
- actions/refresh-board.md 12 KB
- actions/refresh-living-spec.md 10 KB
- actions/research.md 11 KB
- actions/review.md 14 KB
- actions/status.md 9.9 KB
- actions/subplan.md 9.2 KB
- agents/orchestrator.md 6.9 KB
- agents/researcher.md 4.9 KB
- agents/reviewer.md 6.2 KB
- evals/evals.json 8.6 KB
- lib/schemas.md 9.1 KB
- lib/state.md 33 KB
- PORTABILITY.md 2.6 KB
- profiles/_shared/board/index.html 150 KB
- profiles/_shared/explorer/index.html 275 KB
- profiles/_shared/explorer/index.src.html 75 KB
- profiles/_shared/plans-index/index.html 176 KB
- profiles/_shared/plans-index/index.src.html 35 KB
- profiles/_shared/profile.json 418 B
- profiles/_shared/templates/00-README.md 6.2 KB
- profiles/_shared/templates/01-plan.md 1.6 KB
- profiles/_shared/templates/02-research-external.md 746 B
- profiles/_shared/templates/03-research-internal.md 564 B
- profiles/_shared/templates/04-discussion.md 516 B
- profiles/_shared/templates/05-tracking.md 3.4 KB
- profiles/_shared/templates/artifact/assets/.gitkeep 0 B
- profiles/_shared/templates/artifact/assets/README.md 538 B
- profiles/_shared/templates/artifact/data/.gitkeep 0 B
- profiles/_shared/templates/artifact/data/README.md 2.1 KB
- profiles/_shared/templates/artifact/index.html 37 KB
- profiles/_shared/templates/artifact/manifest.json 1.0 KB
- profiles/_shared/templates/artifact/orchestrate.workflow.js 5.1 KB runs code
- profiles/_shared/templates/drafts/README.md 3.3 KB
- profiles/_shared/templates/subplans/bug-doc.md 2.9 KB
- profiles/_shared/templates/subplans/decision-doc.md 2.5 KB
- profiles/_shared/templates/subplans/diff-plan.md 3.7 KB
- profiles/content/explorer/index.html 273 KB
- profiles/content/profile.json 432 B
- profiles/content/templates/01-plan.md 3.5 KB
- profiles/content/templates/05-tracking.md 2.7 KB
- profiles/design-system/explorer/index.html 273 KB
- profiles/design-system/profile.json 803 B
- profiles/design-system/templates/00-README.md 4.3 KB
- profiles/design-system/templates/01-plan.md 3.5 KB
- profiles/design-system/templates/05-tracking.md 2.8 KB
- profiles/design-system/templates/parts-template.md 2.9 KB
- profiles/design-system/templates/quality-gate.md 2.7 KB
- profiles/film/profile.json 467 B
- profiles/film/templates/01-plan.md 7.3 KB
- profiles/film/templates/05-tracking.md 5.3 KB
- profiles/general/profile.json 455 B
- profiles/general/templates/01-plan.md 1.2 KB
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.
- 7d ago First seen · 275 lines · 416 tokens per session scan A e2c7361b33d6
groundwork is a skill published in the GitHub repository ikenga-hq/ikenga-pkgs (0 stars, last pushed today), licensed Apache-2.0. It adds 416 tokens to every session and 5,798 once invoked, about $0.0021 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…