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/ayghri/overleaf-mcp/contributingnpx skills add ayghri/overleaf-mcp --skill contributinggit clone --depth 1 https://github.com/ayghri/overleaf-mcpWrote 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/ayghri/overleaf-mcp/contributing)<a href="https://agentmods.dev/skills/ayghri/overleaf-mcp/contributing"><img src="https://agentmods.dev/badge/skills/ayghri/overleaf-mcp/contributing.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.00070 | $0.01816 |
| Opus 5 | $0.00035 | $0.00908 |
| Sonnet 5 | $0.00014 | $0.00363 |
| Haiku 4.5 | $0.00007 | $0.00182 |
Grade A, and why
contributing 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 4d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to OverleafMCP
An MCP server that drives an Overleaf project as a live collaborator. Read this
before changing overleaf_mcp/. Keep the four invariants below intact — they are
safety- and correctness-critical, not stylistic.
Hard invariants (do not weaken)
- Review mode is enforced in code, not by the account role. Every edit is a
tracked-change suggestion:
apply_opalways attaches ameta.tcid and never branches on permission level. Even if the bot account were promoted to full editor, the MCP must still only suggest. Never add a "direct write" path. - Edit by the content-anchored cursor, never by raw line numbers. Placement
is
goto_text(content) /goto_file; the cursor is a character offset that is OT-transformed on every incoming edit (_transform_offset), so it stays pinned while a human types. Line-number-based mutation is a known bug source and is banned in the edit tools.select_to_textmust search FORWARD from the cursor (_find_nth_from), not globally — a global search once resolved a repeated anchor (\end{proof}) to an earlier occurrence and selected backward over 27k chars. Keep the forward default; backward needsallow_backward. - Reads are served from the live cache and must not move the cursor. Only
goto_file/goto_textand edits move the cursor.read_file/search/list_filesnever do. - Latency budget: interactive actions target ≤50ms (see below). Anything that can be served from the in-memory subscription must not do a network round-trip.
Tracked-change gotchas
- Overleaf merges adjacent same-author tracked ranges. So a change's live
length (from
list_changes) can grow after a neighbouring edit — undoing a deletion re-inserts text next to an insertion, and the two fuse. Any op that acts on a change by id (undo_change,revise_change) must not assume the range is the length you created it at;undo_changetakesexpect_charsto assert this. Don't reintroduce blind by-id deletion. undo_changeon a deletion re-inserts (reviewers can't reject), so it is not truly "zero residual" — it leaves a content-neutral insert+delete pair. Prefer fixing the selection up front over undo-chaining.
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.
- 4d ago First seen · 135 lines · 70 tokens per session scan A c2decb72c0b0
contributing is a skill published in the GitHub repository ayghri/overleaf-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 1,816 once invoked, about $0.0003 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 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…