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 Tradebaas/Groundwork --skill stackgit clone --depth 1 https://github.com/Tradebaas/GroundworkWrote 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/tradebaas/groundwork/stack)<a href="https://agentmods.dev/skills/tradebaas/groundwork/stack"><img src="https://agentmods.dev/badge/skills/tradebaas/groundwork/stack/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/tradebaas/groundwork/stack"><img src="https://agentmods.dev/badge/skills/tradebaas/groundwork/stack.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.00000 | $0.01853 |
| Opus 5.5 | $0.00000 | $0.00741 |
| Sonnet 5.5 | $0.00000 | $0.00371 |
| Haiku 4.5 | $0.00000 | $0.00185 |
Grade A, and why
stack 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 6d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stack: choose deliberately, then be born current
"Stack" here means whatever the product is built on: a language and framework on self-chosen infrastructure, or a hosted platform where the product is largely configured (Power Platform, ServiceNow, Salesforce, Google's builders, or any successor). This skill carries a method, not a platform table; every platform fact is looked up live from the vendor's current official documentation, so platforms and practices that appear after this skill was written are in scope automatically.
1. Decide the stack: options on merit
Derive candidates from BRIEF.md (target, users, constraints, integrations, team). Hosted platforms are candidates on equal footing when the brief points there (existing tenant, licensing, citizen-developer handover). Present 2-3 genuinely different options with honest trade-offs (fit, ecosystem maturity, hiring/handover, cost, compliance implications, e.g. EU data residency of managed services). Recommend one; the owner confirms. Record as a decision record with the options and the reason.
Verify before recommending. Versions, support status, pricing, EU-residency: check current authoritative sources (official docs, release pages). Model memory is a rumor with a cutoff.
2. Generate docs/standards/<stack>.md
Existing project: read what the code already does before writing a rule. The linter and formatter it configures, the test runner and where the tests live, the module layout, the naming in use, the stages its CI runs: these are the standards the project has, and the file records them first. A convention the code follows stays unless it fails the floor; a new one arrives with its reason and its migration path, never by a rewrite of what works.
Start from docs/standards/TEMPLATE-STACK.md, which owns the shape. Its floor table is the part
checks/check.mjs reads: six classes of risk, each answered with a command, a reasoned
not applicable, or a named manual check with a defer: marker. Fill that table as you
research, because it is what step 3 has to satisfy.
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.
- 6d ago Changed · -24 lines 82b4d84a7be0
- 1mo ago Changed · +15 lines · -98 tokens per session f50edf6e932b
- 1mo ago First seen · 129 lines · 98 tokens per session scan A b7a061b4cf12
stack is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,853 tokens. 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
mission-driver
Create roadmaps and mission configs, then drive the mission-driver AI dev-loop engine. mission-driver lives at tools/mission-driver/ — it reads missions/ .json and loops CHECK → REVIEWPLANS → EXECPLANS → DRAFTPLANS → DEEPAUDIT until the roadmap is done or the audit budget is exhausted. Use this skill when the user…
keel-plan
Create or revise PLAN.md — propose the phase DAG (phases · gates · dependencies) from the user's goal, get approval, write the table and regenerate the colored Mermaid diagram from it. Statuses flip at rituals (/keel-handover, /keel-phase-review); post-completion fixes land in the Fix log.
keel-stats
Render the ritual telemetry visually — turns .claude/ritual-log into reports/ritual-stats.md with PLAN.md-style colored Mermaid interval boxes (session/compact boundaries) + a counts table, plus git-derived PROCESS metrics (process-only commit share · LOC by class · always-loaded KB · last test-log age · Review…
autonomous-build
Execute a local task register with requirement tracing, verification, review, and refinement.
ship
Verify changes and perform only explicitly requested Git steps: commit, push, or draft PR. Never infer publication authority.
init
Configure an uninitialized project from the active SPEC.md contract and verify the local stack.