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/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/remove-ip)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/remove-ip"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/remove-ip/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/davistroy/claude-marketplace/remove-ip"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/remove-ip.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.00017 | $0.03281 |
| Opus 5 | $0.00009 | $0.01640 |
| Sonnet 5 | $0.00003 | $0.00656 |
| Haiku 4.5 | $0.00002 | $0.00328 |
Grade A, and why
remove-ip 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 9d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Company De-Identification and IP Sanitization
Remove company-identifying information and intellectual property from documents to prevent re-identification while preserving maximum meaning, structure, and usefulness.
Input Validation
Required Arguments:
<document-path>- Path to the document to sanitize
Optional Arguments:
--company <name>- Company name to redact (auto-detected if not provided)--mode [standard|strict]- Sanitization mode (default: standard)standard: Preserve maximum context while removing identifiers and likely non-public IPstrict: Assume adversarial re-identification attempts; default to redacting anything specific
--industry <industry>- Industry context (helps with generalization)--audience <audience>- Intended audience of sanitized version--web-research [yes|no]- Allow web research for public info verification (default: yes in standard, no in strict)--no-prompt- Skip interactive prompts and ambiguity questions. Apply safe defaults for all decisions (default to more redaction when uncertain).
Validation: If the document path is missing:
- If
--no-promptis specified, display the error and exit:
Error: Missing required argument
Usage: /remove-ip <document-path> [options]
Example: /remove-ip internal-process.md
Example: /remove-ip strategy-doc.md --mode strict
- Otherwise (default), display the full usage help:
Usage: /remove-ip <document-path> [options]
Options:
--company <name> Company name to redact (auto-detected if omitted)
--mode [standard|strict] Sanitization mode (default: standard)
--industry <industry> Industry context for generalization
--audience <audience> Intended audience of sanitized version
--web-research [yes|no] Allow web research (default: yes for standard, no for strict)
--no-prompt Skip interactive prompts, apply safe defaults
Examples:
/remove-ip internal-process.md
/remove-ip strategy-doc.md --mode strict
/remove-ip playbook.md --company "Acme Corp" --industry "Finance"
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.
- 9d ago First seen · 326 lines · 17 tokens per session scan A fe530634d70a
remove-ip is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 3,281 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other commands, from other repositories
sign
Sign a PDF — stamp a signature block (name + date, or a PNG signature) on a signed copy.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).
lawsuit-analysis
A command that analyses legal case documents and produces a structured, self-contained HTML report. It can organise people, claims, responses, evidence, and events from documents such as complaints or briefs.
template-fill
A command that fills registered spreadsheet legal templates with information extracted from PDFs or images. It can use documents from the current case and shared template locations.
legal-risk
Analyze sourced covenant clauses and merger-agreement MAC/MAE language with page-level quotes and risk classification.
arckit.fr-marche-public
You are helping an enterprise architect generate French public procurement documentation (Dossier de Consultation des Entreprises) aligned with the Code de la Commande Publique, UGAP, and DINUM digital doctrine requirements.