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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/commands/evan043/claude-cli-advanced-starter-pack/repo-guard.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/repo-guard.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/repo-guard.template/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/commands/evan043/claude-cli-advanced-starter-pack/repo-guard.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/repo-guard.template.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.00000 | $0.00459 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
repo-guard.template 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 10d 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.
What it actually says
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Pre-commit guard - run UI tests and lint checks before committing
Repository Guard
Pre-commit quality gate that runs Neovim UI tests, checks for common issues, and prevents commits with broken UI.
Usage
/repo-guard
/repo-guard --quick
/repo-guard --full
Checks Performed
Quick Mode (default)
- Lua syntax - Check all .lua files parse without errors
- Module loads - Verify all ccasp modules can be required
- Smoke test - Run ui_smoke_spec.lua
Full Mode
- Everything in quick mode, plus:
- Full test suite - All spec files
- Layout snapshot - Compare with last known-good snapshot
- Keymap validation - All keymaps registered correctly
Protocol
When the user runs /repo-guard:
- Determine mode (quick or full)
- Run Lua syntax check:
nvim --headless -c "luafile nvim-ccasp/lua/ccasp/init.lua" -c "qa" - Run smoke test:
./scripts/nvim-smoke.ps1 - If full mode, run:
./scripts/nvim-test.ps1 - Report results with pass/fail for each check
- If all pass: "Safe to commit"
- If any fail: "Fix issues before committing" with 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.
- 10d ago First seen · 51 lines · 0 tokens per session scan A 13a92489a773
repo-guard.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 459 tokens. 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-30.
Other commands, from other repositories
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
ship-csk
DoD gate + commit proposal (waits for approval).
commit
Analyze changes and create atomic, conventional commits with intelligent message generation, version management, changelog updates, and quality insights.
block-no-verify
Set up PreToolUse hook to block --no-verify and other git bypass flags in Claude Code projects.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.