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 mitodl/agent-kit --skill validate-before-commitgit clone --depth 1 https://github.com/mitodl/agent-kitWrote 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/mitodl/agent-kit/validate-before-commit)<a href="https://agentmods.dev/skills/mitodl/agent-kit/validate-before-commit"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/validate-before-commit/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/mitodl/agent-kit/validate-before-commit"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/validate-before-commit.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.00059 | $0.00634 |
| Opus 5.5 | $0.00024 | $0.00254 |
| Sonnet 5.5 | $0.00012 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
validate-before-commit 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 16d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Before Commit
Do not declare a task done until the full validation sequence has passed. Run these checks proactively — do not wait for the human to ask.
Standard sequence
# 1. Linting, formatting, and basic static checks
uv run prek run --all-files
# 2. Type checking
uv run mypy <package_or_src_dir>
# 3. Infrastructure plan (if Pulumi files were changed)
pulumi preview --stack <stack-name>
mitodl repositories run their hooks with prek, which
reads the same .pre-commit-config.yaml (or prek.toml) that pre-commit
did. Use the command for the repository's prek pin:
| Repository | Hook command |
|---|---|
Python with uv (prek in the prek dependency group) |
uv run prek run --all-files |
Node (@j178/prek in devDependencies) |
npx prek run --all-files |
| Neither (prek installed as a tool) | prek run --all-files |
Not yet migrated (still uses pre-commit) |
uv run pre-commit run --all-files in a uv project, otherwise pre-commit run --all-files |
In a repository with .github/workflows/autofix.yml, the same hooks run in CI
as the prek check. When the hooks' only problems are ones they fixed
themselves, autofix.ci commits those fixes to the PR, except under .github/.
If any hook still fails, nothing is committed and the check stays red.
Running the hooks locally first avoids both.
Rules
- Run the hooks before mypy; they may auto-fix formatting that would otherwise produce mypy noise.
- If the hooks auto-fix files, stage the changes and re-run them to confirm every hook passes cleanly.
- mypy errors are blocking — do not leave type errors for the human to clean up.
pulumi previewoutput must be reviewed: unexpected replacements or deletions are bugs, not acceptable side effects.
For Dagster / dg changes
After modifying assets, sensors, or code location structure, also confirm the workspace loads cleanly:
dg check
Interpreting failures
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.
- 16d ago Changed · +17 lines · +3 tokens per session 96a2783a7072
- 1mo ago First seen · 55 lines · 56 tokens per session scan A 053dc81366e6
validate-before-commit is a skill published in the GitHub repository mitodl/agent-kit (5 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 59 tokens to every session and 634 once invoked, about $0.0002 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.
Other skills, from other repositories
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.