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/divide-by-0/autolatex/apps-script-pushnpx skills add Divide-By-0/autolatex --skill apps-script-pushgit clone --depth 1 https://github.com/Divide-By-0/autolatexWhat 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.00048 | $0.01468 |
| Opus 5 | $0.00024 | $0.00734 |
| Sonnet 5 | $0.00010 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
apps-script-push 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 2d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apps Script Push
Use this workflow for any request to push code from this repo to the remote Apps Script project.
Push Commands
Common: runclasp pushfrom Common/.clasp.json.Docs: runnpm run clasp-pushfrom Docs/package.json.Slides: runnpm run clasp-pushfrom Slides/package.json.Sheets: runnpm run clasp-pushfrom Sheets/package.json. Sheets is a real SpreadsheetApp-based project as of 2026-05-18 (previously it was a stale DocumentApp fork); it links Common like Docs/Slides do.
Production Safety
Treat production Apps Script projects as live user-impacting systems.
Do not hard-code production script IDs in this skill. If production IDs are needed for target checks, load them from a local untracked .env file:
AUTOLATEX_PROD_COMMON_SCRIPT_IDAUTOLATEX_PROD_DOCS_SCRIPT_IDAUTOLATEX_PROD_SLIDES_SCRIPT_ID— the live Slides Marketplace add-on; whatSlides/.clasp.jsonpoints at by default.AUTOLATEX_PROD_SLIDES_VERSIONS_SCRIPT_ID— separate Slides project where new prod versions are cut before the SDK App Config flips to them. Not the live add-on, but still production-adjacent.AUTOLATEX_TEST_SLIDES_SCRIPT_ID— Slides sandbox for ad-hoc testing; safe to push freely.
Do not push test or debugging changes to these production projects unless the user explicitly asks for a production push or restore. This is especially important for Common: some already-published Docs versions may reference Common with version: "0" and developmentMode: true, so pushing Common HEAD can immediately change production behavior without a new Docs version or Marketplace publish.
For testing, use the Slides test sandbox (AUTOLATEX_TEST_SLIDES_SCRIPT_ID) or a separate Apps Script project, not production Common, Docs, or the live Slides add-on. Before any push, print the target .clasp.json script ID and say which env-var (if any) it matches, or that it cannot be classified because .env is missing.
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.
- 2d ago First seen · 96 lines · 48 tokens per session scan A 231a8ecac783
apps-script-push is a skill published in the GitHub repository Divide-By-0/autolatex (49 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,468 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…