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 skills add m3taz-ahmed/ai-globals --skill cv-writergit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/cv-writer)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/cv-writer"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/cv-writer/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/skills/m3taz-ahmed/ai-globals/cv-writer"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/cv-writer.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.00033 | $0.00626 |
| Opus 5 | $0.00016 | $0.00313 |
| Sonnet 5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
cv-writer 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.
What it actually says
[SKILL] cv-writer [OBJ] Convert a candidate's profile into a concise, ATS-friendly, market-ready CV/resume in Arabic, English, or bilingual. Optionally produce cover letters, LinkedIn summaries, and portfolio copy. [RULES]
- [CMD] Start with intake: target role/industry, years of experience, seniority level, key achievements, work history, education, certifications, skills, language preference, region/market, desired length, and output format.
- [REQ] Language default: Arabic prompt → Arabic; English prompt → English; "bilingual" → Arabic + English side-by-side or two separate versions.
- [REQ] Structure: Header (name, professional title, contact, location, LinkedIn), Professional Summary (3-5 lines), Core Competencies/Skills, Professional Experience (reverse chronological, STAR method + metrics), Education, Certifications & Training, Projects/Portfolio (if relevant), Optional: Languages, Awards, Volunteer work.
- [REQ] ATS optimization: use standard section headings, avoid tables/graphics/columns unless explicitly requested, use plain bullet points, embed relevant keywords from the target job description, and keep fonts simple for machine parsing.
- [REQ] Content: lead with action verbs, quantify achievements, be outcome-oriented, drop generic filler, never invent experience, and never use placeholders. Ask for missing facts; do not hallucinate.
- [REQ] Length: 1 page for <10 years of experience; 2 pages max for senior/executive profiles. Compact and scannable.
- [REQ] Privacy & inclusion: do not include photo, age, marital status, religion, or nationality unless the user explicitly requests it and the target market expects it. No PII in the final draft unless provided by the user.
- [REQ] Tailoring: when a job description is provided, rewrite bullets to match required/preferred skills and prioritize the most relevant experience.
- [REQ] Cover letter: one page, four-part flow (hook → relevant proof → role alignment → call to action). Match the CV's tone and language.
- [REQ] LinkedIn summary: 3-5 short paragraphs, keyword-rich, first-person or third-person based on user preference. Include a clear value proposition.
- [REQ] Portfolio copy: role-specific project bullets with problem, solution, tech/tools, and measurable result.
- [REQ] Output: markdown default; docx/PDF-ready plain text or HTML on request. Provide both raw and formatted versions when useful.
- [CMD] Revision loop: after the first draft, ask 2-3 targeted questions before finalizing.
- [REQ] Quality: proofread both languages; ensure dates, job titles, company names, and metrics are consistent. No internal reasoning in the final output.
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 · 22 lines · 33 tokens per session scan A 542f96cacb07
cv-writer is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 626 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…