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/hlalljie/agent-workflow-presets/verify-commitnpx skills add hlalljie/agent-workflow-presets --skill verify-commitgit 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.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00672 |
| Opus 5 | $0.00021 | $0.00336 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 3d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify commit
Role
Spawn as a subagent using [MODEL:verifier]. 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
If the diff moved, renamed, or deleted files/exports/types: grep docs/, tests/manual/, .cursor/rules/ for stale paths. FAIL if any active doc references a path or symbol that no longer exists. Key docs to check: docs/folder-structure.md and .cursor/rules/repository-layout.mdc, plus any domain docs listed there. Skip when the diff only changed logic without touching file paths or public names.
3. Scoped review (changed code only)
Light fit-in-repo pass.
- Check for layer violations, surface mismatches, duplication (see check-shared-before-scoped.mdc), missing tests, and noise. For large diffs, spawn an explore subagent using
[MODEL:researcher]to scan before reviewing.
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.
- 3d 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 1mo ago), licensed MIT. It adds 42 tokens to every session and 672 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
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
install-from-remote-library
Use when installing skills from a shared ai-agent-skills library repo. Inspect with --list first, prefer --collection, and preview with --dry-run before installing.