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 beel-collab/presets.dev --skill codebase-audit-pre-pushgit clone --depth 1 https://github.com/beel-collab/presets.devWrote 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/beel-collab/presets.dev/codebase-audit-pre-push)<a href="https://agentmods.dev/skills/beel-collab/presets.dev/codebase-audit-pre-push"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/codebase-audit-pre-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.00031 | $0.02035 |
| Opus 5 | $0.00015 | $0.01018 |
| Sonnet 5 | $0.00006 | $0.00407 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
codebase-audit-pre-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 4d 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
95% identical to codebase-audit-pre-push — 18 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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Push Codebase Audit
As a senior engineer, you're doing the final review before pushing this code to GitHub. Check everything carefully and fix problems as you find them.
When to Use This Skill
- User requests "audit the codebase" or "review before push"
- Before making the first push to GitHub
- Before making a repository public
- Pre-production deployment review
- User asks to "clean up the code" or "optimize everything"
Your Job
Review the entire codebase file by file. Read the code carefully. Fix issues right away. Don't just note problems—make the necessary changes.
Audit Process
1. Clean Up Junk Files
Start by looking for files that shouldn't be on GitHub:
Delete these immediately:
- OS files:
.DS_Store,Thumbs.db,desktop.ini - Logs:
*.log,npm-debug.log*,yarn-error.log* - Temp files:
*.tmp,*.temp,*.cache,*.swp - Build output:
dist/,build/,.next/,out/,.cache/ - Dependencies:
node_modules/,vendor/,__pycache__/,*.pyc - IDE files:
.idea/,.vscode/(ask user first),*.iml,.project - Backup files:
*.bak,*_old.*,*_backup.*,*_copy.* - Test artifacts:
coverage/,.nyc_output/,test-results/ - Personal junk:
TODO.txt,NOTES.txt,scratch.*,test123.*
Critical - Check for secrets:
.envfiles (should never be committed)- Files containing:
password,api_key,token,secret,private_key *.pem,*.key,*.cert,credentials.json,serviceAccountKey.json
If you find secrets in the code, mark it as a CRITICAL BLOCKER.
2. Fix .gitignore
Check if the .gitignore file exists and is thorough. If it’s missing or not complete, update it to include all junk file patterns above. Ensure that .env.example exists with keys but no values.
3. Audit Every Source File
Look through each code file and check:
Dead Code (remove immediately):
- Commented-out code blocks
- Unused imports/requires
- Unused variables (declared but never used)
- Unused functions (defined but never called)
- Unreachable code (after
return, insideif (false)) - Duplicate logic (same code in multiple places—combine)
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.
- 4d ago First seen · 246 lines · 31 tokens per session scan A c5e024bd48bf
codebase-audit-pre-push is a skill published in the GitHub repository beel-collab/presets.dev (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 2,035 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to codebase-audit-pre-push, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
code-review-recent-changes
Review recent changes since a fixed point (commit, branch, tag, or merge-base) across three independent axes - Standards, Spec, and Maintainability - producing severity-ordered findings with an explicit verdict. Use when the user wants to review a branch, a PR, or recent committed changes.
code-review
Use this skill after completing multiple, complex software development tasks before informing the user that work is complete.
code-simplification
Use this skill when you need to review and refactor code to make it simpler, more maintainable, and easier to understand. Helps with identifying overly complex solutions, unnecessary abstractions.
self-review
Use to critically self-review your changes, or when you want to delegate the review to a sub-agent.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by whatever domain language and architectural decisions are already documented in the repo. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).