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 agentmods add commands/echoingvesper/mcp-task-orchestrator/secrets-scanner-fixgit 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.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 | $0.00000 | $0.01544 |
| Opus 5 | $0.00000 | $0.00772 |
| Sonnet 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 5d 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.
- 5d 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
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.
proyecto
Declara el proyecto activo (scope global) para atribucion de coste/horas en agentactions. Sin argumento, muestra el proyecto actual.
argos
설계 산출물 대비 구현 검증 — 준공검사 감리 (아르고스).
handover
Works for you. Go outside and live. — AI orchestrator that auto-routes tasks to the cheapest model that solves them. 70% run free on local models. Self-auditing, self-improving, zero prompting skill needed. Built with vibe coding by a finance student. Your models, your data.
instinct-status
Shows learned instincts from dqiii8.db, grouped by project and confidence. Internal diagnostic tool — not for user invocation.
test-team
Works for you. Go outside and live. — AI orchestrator that auto-routes tasks to the cheapest model that solves them. 70% run free on local models. Self-auditing, self-improving, zero prompting skill needed. Built with vibe coding by a finance student. Your models, your data.