Borrowing it
Nothing to install: this file belongs to HozaifaMoustafa/hozaifamoustafa-resume-latex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HozaifaMoustafa/hozaifamoustafa-resume-latex/main/CLAUDE.mdgit clone --depth 1 https://github.com/HozaifaMoustafa/hozaifamoustafa-resume-latexWrote 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/instructions/hozaifamoustafa/hozaifamoustafa-resume-latex/claude-md)<a href="https://agentmods.dev/instructions/hozaifamoustafa/hozaifamoustafa-resume-latex/claude-md"><img src="https://agentmods.dev/badge/instructions/hozaifamoustafa/hozaifamoustafa-resume-latex/claude-md/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/instructions/hozaifamoustafa/hozaifamoustafa-resume-latex/claude-md"><img src="https://agentmods.dev/badge/instructions/hozaifamoustafa/hozaifamoustafa-resume-latex/claude-md.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.00793 | $0.00793 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
hozaifamoustafa-resume-latex CLAUDE.md 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 12d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions — hozaifamoustafa-resume-latex
This repo is a LaTeX resume template with an HR-informed guide. When a developer opens it with a coding agent, there are two primary workflows you should support.
Workflow 1: Build or Improve the Resume
Triggered by: "help me build my resume", "edit my resume", "update my resume", "I want to apply for X role", or any request to modify resume content.
How to conduct this
- Read
RESUME_GUIDE.mdin full — it is the authoritative source for every structural and content decision. - Read
hozaifamoustafa_resume.tex— this is the file to edit. - Ask the user for the following if not already provided:
- Their target role
- Their degree field vs. the target role field (same domain or different?)
- Years of experience
- Apply section ordering based on the rule in
RESUME_GUIDE.mdSection 1:- Same domain → Education before Experience
- Different domain → Experience before Education
- Edit the
.texfile directly. Follow every constraint in the guide: quantified bullets, action verbs, correct section order, no personal info beyond what is listed, ATS-safe structure. - Do not add sections that are not in the guide. Do not invent content — only use what the user provides.
- Compile check: remind the user to run
pdflatex hozaifamoustafa_resume.texto generate the PDF.
Key files
| File | Purpose |
|---|---|
hozaifamoustafa_resume.tex |
The resume source — edit this |
RESUME_GUIDE.md |
HR criteria, section ordering rules, formatting constraints |
Workflow 2: Gap Analysis — "What Am I Missing?"
Triggered by: "what am I missing?", "what should I build next?", "how do I strengthen my resume?", "what projects should I focus on?", or any question about technical gaps.
How to conduct this
- Read
RESUME_GUIDE.mdSection 13 — it contains the full role-to-gap mapping table. - Read the user's current resume (either
hozaifamoustafa_resume.texor ask them to paste their Projects and Skills sections). - Ask the user for their target role if not clear from context.
- Compare their current projects and skills against the required proof points for that role in the Section 13 table.
- Identify the specific proof point that is absent or weakly represented.
- Recommend the exact project from the table. Be concrete:
- Project name (meaningful, not generic)
- Tech stack
- Scope (achievable in 1–2 weeks)
- What the deployed artifact looks like (link, installable, notebook, etc.)
- How to write it on the resume once built
- For a structured prompt the user can take to any LLM, refer them to
gap_analysis_prompt.md.
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.
- 12d ago First seen · 67 lines · 793 tokens per session scan A d47f4e19b46e
hozaifamoustafa-resume-latex CLAUDE.md is an instructions file published in the GitHub repository HozaifaMoustafa/hozaifamoustafa-resume-latex (107 stars, last pushed 2mo ago), licensed MIT. It adds 793 tokens to every session, about $0.0040 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).