Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/verify-commit/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/verify-commit)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/verify-commit"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/verify-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/hlalljie/agent-workflow-presets/verify-commit"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/verify-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.00042 | $0.00786 |
| Opus 5.5 | $0.00017 | $0.00314 |
| Sonnet 5.5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
verify-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 19d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify commit
Role
Spawn as a subagent. Check only. Prefer run tests when a test plan or tests/plans/*.md exists so command order matches the slice. Otherwise: npm test, npm run build, npm run test:… / npm run lint from package.json. Manual: run manual browser test. Does not fix code or git commit.
The invoker (e.g. run task loop) runs commit skill after PASS.
Scope
- Files:
git diff/git statussince last commit or user-named paths. - Manual: Matching
tests/manual/*.mdper plan or diff. Run with Start state that uses production build +startso verification matches ship shape; dev-only is insufficient unless the checklist explicitly documents dev and you also pass preview for the same paths. Blocked env → report browser not run (blocked).
1. Automated + manual
- If test plan present → follow run tests then ensure
npm run build(and lint if needed). - Else →
npm test,npm run build, relevantnpm run test:…/npm run lint.
2. Docs freshness
- Dead references (FAIL). If the diff moved, renamed, or deleted files/exports/types: grep
docs/,tests/manual/,.cursor/rules/, andREADME.mdfor stale paths. FAIL if any active doc references a path or symbol that no longer exists. Key docs to check:docs/folder-structure.md, every doc it lists, and.cursor/rules/repository-layout.mdc. Skip when the diff did not touch file paths or public names. - Likely stale content (warning). Use the "What does this change need?" list in write-docs. If the diff changed something a doc covers (a flow, an env var, an ops step, a decision) and that doc is not in the diff, add it to Docs to update in the report. Do not FAIL for it, and do not edit the doc: the invoker updates it.
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.
- 19d ago Changed · +1 lines 81704a341ce8
- 22d ago Changed 79e50435247c
- 1mo ago First seen · 43 lines · 42 tokens per session scan A 6bbc28c609bd
verify-commit is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 42 tokens to every session and 786 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
workflow-patterns
Systematic task implementation using TDD, phase checkpoints, and structured commits. Ensures quality through red-green-refactor cycles, 80% coverage gates, and verification protocols before proceeding.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
create-prove
Run a changed Aeon skill for real and attach SHA-bound behavioral evidence to its PR.
coverage-drop-investigator
Use when test coverage has dropped and you need to find which changes caused it and what tests to add. Traces coverage regressions to specific commits and files.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.