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 mracal/vibe-engineering --skill pre-commit-auditgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/pre-commit-audit)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/pre-commit-audit"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/pre-commit-audit/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/mracal/vibe-engineering/pre-commit-audit"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/pre-commit-audit.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.00035 | $0.00568 |
| Opus 5.5 | $0.00014 | $0.00227 |
| Sonnet 5.5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
vibe-pre-commit-audit 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 1mo 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.
This is a copy
100% identical to vibe-pre-commit-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-pre-commit-audit
Catch the easy mistakes before they enter history.
When to Use This Skill
- Before creating a git commit
- When reviewing your own staged changes
- Before pushing to a shared branch
When NOT to Use This Skill
- Commits to personal scratch branches
- When the user explicitly says to skip checks
- Auto-generated code commits (lock files, etc.)
Checks
1. Secrets & Credentials
Scan for patterns:
API_KEY=,SECRET=,PASSWORD=,TOKEN=- AWS keys:
AKIA[0-9A-Z]{16} - Private keys:
-----BEGIN.*PRIVATE KEY----- - Connection strings with credentials
.envfiles being staged
2. Debug Statements
console.log(,fmt.Println(,print(,debugger;// DEBUG,# DEBUG,/* DEBUGlog.Debugin non-debug code paths
3. TODOs Without References
TODOwithout issue number:TODO: fix this(bad)TODO(#123): fix this(good)FIXME,HACK,XXX— flag all
4. Disabled Tests
t.Skip(,xit(,xdescribe(,@pytest.mark.skip- Commented-out test functions
//nolintwithout justification
5. Large Files
- Files > 1MB
- Binary files (images, compiled assets)
- Lock files with excessive changes
6. Commented-Out Code
- Blocks of 3+ consecutive commented-out lines of code
- Not comments explaining code, but actual code that's commented out
Output Format
Pre-Commit Audit
Status: CLEAN / WARNINGS / BLOCKED
| Check | Status | Findings |
|---|---|---|
| Secrets | ✓/✗ | X patterns found |
| Debug statements | ✓/✗ | X occurrences |
| TODOs | ✓/◐ | X without references |
| Disabled tests | ✓/✗ | X found |
| Large files | ✓/✗ | X over limit |
| Commented code | ✓/◐ | X blocks |
Blocking Issues (must fix)
- [Secret found in file.go:42]
Warnings (should fix)
- [TODO without reference in handler.ts:15]
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.
- 1mo ago First seen · 77 lines · 35 tokens per session scan A 8cbf22ba25f1
vibe-pre-commit-audit is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 7d ago), licensed MIT. It adds 35 tokens to every session and 568 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-pre-commit-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.