Borrowing it
Nothing to install: this file belongs to ai-ecoverse/slicc. 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/ai-ecoverse/slicc/main/.agents/skills/verifying-before-push/SKILL.mdgit clone --depth 1 https://github.com/ai-ecoverse/sliccWrote 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/ai-ecoverse/slicc/verifying-before-push)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/verifying-before-push"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/verifying-before-push.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.1 | $0.00129 | $0.04663 |
| Opus 5 | $0.00064 | $0.02331 |
| Sonnet 5 | $0.00026 | $0.00933 |
| Haiku 4.5 | $0.00013 | $0.00466 |
Grade A, and why
verifying-before-push 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 yesterday.
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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verifying-before-push
Run the full verification pass before committing, pushing, or opening or updating a PR.
These commands mirror the CI gates in
.github/workflows/ci.yml; running them locally first
is the fastest way to avoid a red PR.
Quick Reference
npm run verify
npm run typecheck
npm run test
npm run test:coverage
npm run build
npm run build -w @slicc/chrome-extension
npm run bundle-size
node packages/dev-tools/tools/check-touched-exemptions.mjs
Run npm run verify first because formatting is the most common CI failure. Do not omit the
separate check-touched-exemptions.mjs command: npm run verify does not include it.
npm run bundle-size needs both builds to have run first — it measures files in dist/.
Pre-push lint gate (automatic)
The .husky/pre-push hook runs the full CI lint gate automatically before every
push to a feature branch. It mirrors every check from the CI lint job —
biome, prettier, custom lint scripts, complexity gate, manifest justifications,
and knip dead-code detection — all in parallel (~6 s wall-clock), then the
autofix-drift check (below) serially, because it writes.
You can also run it manually:
npm run verify # Same gate, run on demand
Escape hatch: git push --no-verify bypasses the gate when needed.
The standard pass
Run every command in order:
npm run verify # Lint gate (mirrors CI lint job)
node packages/dev-tools/tools/check-touched-exemptions.mjs # NOT in npm run verify — easy to miss
npm run typecheck
npm run test
npm run test:coverage # Enforces minimum coverage thresholds
npm run build
npm run build -w @slicc/chrome-extension
npm run bundle-size # Bundle budgets; needs the builds above
The check-touched-exemptions.mjs gate runs right after lint because it catches
grandfathered debt that lint alone misses. See the section below for details.
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.
- yesterday First seen · 340 lines · 129 tokens per session scan A 6767fc122196
verifying-before-push is a skill published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 129 tokens to every session and 4,663 once invoked, about $0.0006 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-09-05.
Other skills, from other repositories
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
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.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.