Borrowing it
Nothing to install: this file belongs to EchoingVesper/mcp-task-orchestrator. 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/EchoingVesper/mcp-task-orchestrator/main/.claude/commands/git-operations/secrets-scanner-fix.mdgit clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestratorWrote 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/echoingvesper/mcp-task-orchestrator/secrets-scanner-fix)<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/secrets-scanner-fix"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/secrets-scanner-fix/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/echoingvesper/mcp-task-orchestrator/secrets-scanner-fix"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/secrets-scanner-fix.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.01544 |
| Opus 5.5 | $0.00000 | $0.00618 |
| Sonnet 5.5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
secrets-scanner-fix 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 2mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Secrets Scanner Fix Command
Usage: /git-operations:secrets-scanner-fix
Purpose: Fix GitHub secret scanning issues by rewriting git history to remove fake secrets from test files while preserving all functionality.
Command Description
This command resolves GitHub push protection violations caused by fake secrets in test files. It uses git filter-branch to rewrite commit history, replacing problematic patterns with safe alternatives that don't trigger secret scanning.
When to Use
- GitHub blocks pushes due to "Push cannot contain secrets"
- Secret scanning detects fake API keys, tokens, or credentials in test files
- Need to clean up commit history without losing work
- Want to maintain test functionality while avoiding security warnings
How It Works
The command will:
- Analyze the Problem: Identify which commits contain problematic patterns
- Plan the Fix: Determine the scope of history rewriting needed
- Execute Filter-Branch: Rewrite commit history to replace fake secrets
- Verify Results: Confirm the fix worked and push is now possible
Interactive Process
The command will guide you through:
# 1. Identify problematic commits and patterns
git log --grep="commit_hash" --oneline
# 2. Backup current state
git branch backup-before-secrets-fix
# 3. Apply history rewriting
git filter-branch --tree-filter [replacement_script] [commit_range]
# 4. Verify and push
git push origin [branch_name]
Common Secret Patterns Fixed
The command automatically replaces these patterns:
| Original Pattern Format | Safe Replacement |
|---|---|
OpenAI API keys (sk-* format) |
FAKE-SK-REDACTED-FOR-TESTING |
GitHub tokens (ghp_* format) |
FAKE-GHP-REDACTED-FOR-TESTING |
Slack bot tokens (xoxb-* format) |
FAKE-XOXB-REDACTED-FOR-TESTING |
Google OAuth tokens (ya29.* format) |
FAKE-YA29-REDACTED-FOR-TESTING |
| JWT Bearer tokens | Bearer FAKE-JWT-REDACTED-FOR-TESTING |
AWS access keys (AKIA* format) |
FAKE-AKIA-REDACTED-FOR-TESTING |
| Custom test keys | REDACTED-FAKE-KEY-FOR-TESTING |
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.
- 2mo ago First seen · 178 lines · 0 tokens per session scan A 5174e315d8b4
secrets-scanner-fix is a command published in the GitHub repository EchoingVesper/mcp-task-orchestrator (28 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,544 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
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
git-ops
Git + worktree orchestrator entry point. /git-ops --landall surveys every branch/worktree and batch-lands the ones that are done; bare /git-ops runs a status survey. Thin router over the git-ops skill.
branch
Show Claude Code costs per git branch / PR.
versioning
Universal version file discovery and sync. Works with any project structure.