Mohamed Mostafa
Mohamed Mostafa's work was selected for the XERJ Corpus Hub, the open reference memory AI coding agents search before they write code. When an agent meets the same problem, it gets this implementation back as a worked example, with the author and the repository attached.
Totals across every corpus @mu-mostafa98 appears in; a commit selected for two corpora counts once. Files and lines count the selected commits; each corpus indexes the whole repository at its pinned commit.
What an agent can do with the servo corpus
servo/servo: Servo aims to empower developers with a lightweight, high-performance alternative for embedding web technologies in applications
- Look up how servo implements rust, browser, webengine, with answers cited to file and line.
- Reuse a worked example: the commit “add the data model” (23 files · Rust).
- Answer from servo's real Rust source instead of memory (Web and frontend platform).
- Where does servo handle “add the data model”?
- How does servo implement rust?
- What does components do in servo?
Search the GitHub repository servo/servo with XERJ (https://hub.xerj.org/corpus/servo--servo). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/servo/servo servo && git -C servo checkout e21d2e4d5886f80d754da0340a788902e788cf3a 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./servo --url http://127.0.0.1:9200 --prefix servo --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: MPL-2.0. Read it for the approach only, do not copy code.
corpus servo--servo · Web and frontend platform
Related corpora: rspack, biome, actix/actix-web, VictorZakharov/better-web-browser
Case study: reference coding for agents
Selected work
servo/servo
The corpus is the whole repository at the pinned commit, not only the files of the selected commit.
Not installable yet: this corpus is not in the hub registry until its licence review passes, so xerj corpus add and xerj ask cannot fetch it. It becomes installable when this card says live in the hub.
Sign in with GitHub or Hugging Face to see more: every selected commit in full (commit date, every folder, licence review state, pin) and the pack builds of each corpus.
[](https://hub.xerj.org/contributors/mu-mostafa98)
Included with the author's permission (email, 2026-10-22), under each repository's own licence, with attribution. Want it removed? Reply to the email or open an issue on xerj-org/xerj.