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/tradebaas/groundwork/verifynpx skills add Tradebaas/Groundwork --skill verifygit clone --depth 1 https://github.com/Tradebaas/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.00046 | $0.00737 |
| Opus 5 | $0.00023 | $0.00368 |
| Sonnet 5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
verify 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 2d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify: evidence, not confidence
A change is verified when its observable behavior matches its acceptance criteria, and you have seen that behavior yourself. "Should work", "compiles", "tests pass" are not that.
1. The floor: every gate green
Run the full chain and paste real results, not summaries of results:
node checks/check.mjs, then the stack gates (typecheck, lint, tests, build; commands are in
docs/standards/<stack>.md). Red gate → stop, fix, rerun. Never weaken a gate to pass it.
2. The point: exercise the change
- Take the spec's acceptance criteria (tier S: the request itself) and walk them end to end in the closest thing to reality available: run the app, call the endpoint, click the flow, render the document. Per criterion: what you predicted you would see → what you did → what you observed. Write the prediction down before running. A pass you did not predict proves only that something happened; a prediction that turns out wrong is the finding, and the real behavior gets explained and traced to a rule before the criterion counts as met.
- Probe the edges the criteria imply: empty input, wrong input, unauthorized user, the second run (idempotency), the slow path. The first bug is usually one step off the happy path.
- User-facing output → also run
design-guardon what rendered. A built interface gets re-checked against its direction contract and the finish verdict; a document, e-mail, export or error string gets judged there in full, because the design method does not carry those. - Bug fix → reproduce the bug first on the old behavior (or its regression test), then show it
gone. A fix you never saw fail is a guess. Cause unknown, or a fix attempt already failed?
Run the
debugskill's loop before trying again.
3. What you cannot verify
Some things this environment can't exercise (production data, real payment, app-store review). Name them explicitly: "verified: A, B; not verifiable here: C, needs , tracked in STATE.md". Unverifiable-and-silent is how "works on my machine" ships.
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.
- 2d ago First seen · 52 lines · 46 tokens per session scan A 1ecef9506898
verify is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 737 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
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. Answers "which skills/commands/hooks ran, how often, in which interval".
sdd-serve
Serve the SDD Builder's AI request queue: claim requests with sddnextrequest, draft the proposal, answer with sddrespondrequest. Never writes spec files — the user accepts each proposal in the builder. Use when the user asks to attend, serve or listen to the SDD board queue. / Atiende la cola de peticiones del SDD…
init
Configure an uninitialized project from an approved charter: stack, scripts, identity, optional Git, and verification.
sdd-workflow
Guide a project with Spec-Driven Development (SDD) discipline - idea, approved spec, consistent plan, tasks, a gate that verifies approval and consent, implementation, validation, and logbook. Bilingual EN/ES. Use when the user wants to start, spec, plan, implement, or validate work with SDD, or mentions specs, plans…