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/scope-guardnpx skills add Tradebaas/Groundwork --skill scope-guardgit 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.00055 | $0.00504 |
| Opus 5 | $0.00028 | $0.00252 |
| Sonnet 5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
scope-guard 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.
What it actually says
scope-guard: before you say "done"
The gates (checks/check.mjs, typecheck, lint, tests) are the floor and must be green. This
checklist catches what they can't see. Answer honestly; the point is the answers, not the ritual.
- Trace. Does every part of this diff trace to a spec, an SC-item in BRIEF.md, or an explicit request? Anything that doesn't → out of the diff, into INTAKE.md.
- Ladder. Did something get built that already existed: in the repo, the platform, or a dependency? Rebuilt-in-disguise counts.
- Minimum. Is there code here for cases nobody asked for: options, abstractions, "flexibility"? Deletion is still cheap now; a month from now it's archaeology.
- While-I-was-here. Any refactors, renames, or cleanups outside the task? Revert them or split them into their own proposed change; never smuggle them along.
- Safety floor intact? Validation at trust boundaries, authorization, data-loss error handling, no silently swallowed failures, secrets, accessibility: none simplified away (AGENTS.md hard rule).
- Deferrals marked. Every deliberate simplification has a
defer:marker with a ceiling and an upgrade trigger, and a DEBT.md row if it will outlive this change. - Done means verified. Has
verifyactually been run on this change, behavior exercised, not just green tools? If not, that's the next step, not this one. - Good is good. Now that it passes: stop. List improvement ideas in INTAKE.md if they're worth keeping; build none of them unasked.
Then update what the change touched: STATE.md (always), the spec status, DEBT.md, stale docs (retired wording → denylist). Report the check's outcome in one or two lines: findings and what you did about them, or "clean". ⚓
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 · 32 lines · 55 tokens per session scan A 79af7e41c62d
scope-guard is a skill published in the GitHub repository Tradebaas/Groundwork (2 stars, last pushed 7d ago), licensed MIT. It adds 55 tokens to every session and 504 once invoked, about $0.0003 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
conventional-commit
Draft a Conventional Commit message when the user requests a commit or message. Formats only; does not authorize Git operations.
keel-autopilot
Gated autonomy for one session — advance phases back-to-back with the full /keel-phase-review run at every gate, auto-commit at phase ends, batch pushes for ONE approval. Stops on gate FAIL, UNCERTAIN decisions, architecture surprises, or security-adjacent changes. Push is never automatic. Solo sessions or an agent…
merge-to-dev
Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.
ship-unit
Commit the built unit as one logical change with a descriptive imperative message.
git-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽入, submit, save, 準備發布, ready to commit, 要推了.
git-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before release, 準備發布.