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 skills/mr-tbot/auto-everything/auto-rewritenpx skills add mr-tbot/Auto-Everything --skill auto-rewritegit clone --depth 1 https://github.com/mr-tbot/Auto-EverythingWrote 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/skills/mr-tbot/auto-everything/auto-rewrite)<a href="https://agentmods.dev/skills/mr-tbot/auto-everything/auto-rewrite"><img src="https://agentmods.dev/badge/skills/mr-tbot/auto-everything/auto-rewrite.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.00097 | $0.04211 |
| Opus 5 | $0.00048 | $0.02106 |
| Sonnet 5 | $0.00019 | $0.00842 |
| Haiku 4.5 | $0.00010 | $0.00421 |
Grade A, and why
auto-rewrite scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST -H 'Content-Type: application/json' \ How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/auto-rewrite
Find code in this repo that came from somewhere else, prove it either way, and give the user real options for clearing it. Two questions per suspect region, in order:
- Is it actually copied? — evidence, not vibes.
- If so, what is the cheapest lawful remedy? — usually not a rewrite.
Not legal advice, and say so once. You are doing engineering triage: locating code, establishing provenance, and costing remedies. A lawyer decides what it means. Name doctrines and cases by name only — never invent a page cite, a docket number, or a section number. A fabricated citation destroys the credibility of a report whose entire value is credibility.
Step 0 — Scope And Trigger
Ask what prompted this, because it sets the depth and the deadline:
| Trigger | Depth |
|---|---|
| Routine hygiene | Passes 1–3, report, no escalation |
| Shipping / open-sourcing soon | Full sweep + remediation applied |
| Acquisition, funding, or enterprise diligence | Full sweep. Say plainly that the acquirer will run a commercial snippet scanner (Black Duck, FOSSID/Revenera, FOSSA, Snyk, Mend) against a far larger proprietary corpus than anything free, so treat your result as a floor, not a ceiling |
| A rightsholder has already made contact | Stop. Escalate before writing findings down — see Escalation |
Then write down the scope: which paths are the user's own work, which are declared third-party
(vendor/, third_party/, Pods/, node_modules/, external/), which are generated, which are
test fixtures. Exclusions get stated in the report — a silent exclusion reads as a clean bill of
health for code nobody looked at.
Declared third-party code is out of scope here and in scope for auto-license-check. The two
skills split on the question: this one asks "did we copy it", that one asks "may we use it".
Pass 1 — Internal Duplication Sweep
Cheap, local, no network. Finds copy-paste inside the repo and gives you the hot files to investigate externally.
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 · 301 lines · 97 tokens per session scan A cf8a5ea44ea7
auto-rewrite is a skill published in the GitHub repository mr-tbot/Auto-Everything (7 stars, last pushed 3d ago), licensed MIT. It adds 97 tokens to every session and 4,211 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
specification-writing
Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…