Borrowing it
Nothing to install: this file belongs to Insight-Services-APAC/ingenious. 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/Insight-Services-APAC/ingenious/main/.claude/commands/git/compush.mdgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/insight-services-apac/ingenious/compush)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/compush"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/compush/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/insight-services-apac/ingenious/compush"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/compush.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.00917 |
| Opus 5.5 | $0.00000 | $0.00367 |
| Sonnet 5.5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
compush 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt: Generate, Commit, and Push with Git
Instructions
-
Security Check: Scan for secrets using detect-secrets
- CRITICAL: Before committing, run detect-secrets to scan for secrets:
# Install if needed: pip install detect-secrets # Scan staged files for secrets git diff --cached --name-only | xargs detect-secrets scan --list-all-secrets- detect-secrets will detect:
- API keys, tokens, passwords
- Private keys, certificates
- Connection strings, database credentials
- AWS/Azure/GCP credentials
- High-entropy strings that may be secrets
- If secrets are found: Remove them immediately, use environment variables or secret management instead
- NEVER commit or push files containing secrets
- For false positives, add to
.secrets.baselinefile
-
Assess the scope of changes
- If there are extensive changes, break them into logical groups
- Each commit should represent a cohesive set of related changes
- Consider grouping by: feature, bug fix, refactoring, documentation, tests
-
Write a commit message using Conventional Commits format
- Use the format:
<type>(<scope>): <description> - Types (required):
feat: New feature or functionalityfix: Bug fixdocs: Documentation changes onlystyle: Code style changes (formatting, whitespace)refactor: Code refactoring without behavior changeperf: Performance improvementstest: Adding or modifying testschore: Build process, dependencies, or tooling changessecurity: Security-related changesci: CI/CD configuration changes
- Scope (optional): Component or module affected (e.g.,
auth,api,db) - Description: Use imperative mood, keep under 50 characters
- Keep the full first line under 72 characters
- NEVER include emojis in commit messages
- Maintain a concise, professional tone
- DO NOT add attribution footers (e.g., no "Generated with Claude Code" or "Co-Authored-By: Claude")
- Use the format:
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 · 124 lines · 0 tokens per session scan A aec9e9174d35
compush is a command published in the GitHub repository Insight-Services-APAC/ingenious (25 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 917 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-09-04.
Other commands, from other repositories
changelog
Generate a structured changelog from recent git commits, categorized by change type.
scm
SCM workflow for Git operations (branching/merge/conflict/worktree) plus Conventional Commit execution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit
Based on the above changes, create a single git commit.
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-pause-work
Create context handoff when pausing work mid-phase.