Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add spinningrachel/career-engine/plugin install career-engineWrote 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/spinningrachel/career-engine/career-engine-export)<a href="https://agentmods.dev/skills/spinningrachel/career-engine/career-engine-export"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/career-engine-export/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/spinningrachel/career-engine/career-engine-export"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/career-engine-export.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.00055 | $0.10325 |
| Opus 5 | $0.00028 | $0.05163 |
| Sonnet 5 | $0.00011 | $0.02065 |
| Haiku 4.5 | $0.00006 | $0.01033 |
Grade A, and why
career-engine-export 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 8d 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 — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Application — DOCX Production
This skill governs all DOCX production in the career-engine pipeline. Load it before any DOCX export step. Output files are .docx, opened directly in Word. The user exports to PDF before sending.
career-datadata root (R-37). The personal-data files —01-writing-rules.md,02-professional-background.md,03-framework.md,linkedin-profile.md,pipeline-preferences.json,delivered-letters/, and the user's.dotx— load from${CAREER_DATA}/references/, the path the orchestrator resolves in itscareer-datadiscovery preflight. Every other file (self-checks,REFERENCES.md, skill docs, default.dotxtemplates) stays on${CLAUDE_PLUGIN_ROOT}. If${CAREER_DATA}is not set (direct or standalone invocation outside the orchestrator), locate thecareer-dataskill yourself, confirmcareer-data-marker.json, and apply the orchestrator's healthy / damaged / absent outcomes before reading. A configured user's missingcareer-datais a hard stop — never silently fall back to blank templates.
The templates own all fonts, sizes, and colors — never hand-set these.
How DOCX production works
cv-writer outputs styled markdown using pandoc's custom-style div and span syntax. The pipeline converts it to .docx at Step 6 using pandoc with the .dotx reference templates. A short post-processing script then updates the role-specific Subtitle in the CV document header.
Templates — fixed-path convention, no config key, never an external OS path (2026-07-04 fix). All templates resolve by fixed filename inside ${CAREER_DATA}/references/templates/ — there is no cv_template or word_templates_path config key anymore, and the plugin never reads a template from outside career-data:
$CV_TEMPLATE=${CAREER_DATA}/references/templates/cv.dotx— CV reference template, Detailed CV Type. Contains all custom styles, the user's name and contact info in the document header, and correct formatting throughout.$CV_TEMPLATE_BRIEF=${CAREER_DATA}/references/templates/cv-brief.dotx— CV reference template, Brief CV Type (one-page, two-column). Required only when the resolved CV Type for a role isBrief— see the CV Type resolution step incareer-engine-new-application/SKILL.md/career-engine-edit/SKILL.md. Never used for a Detailed-type role.$CL_TEMPLATE=${CAREER_DATA}/references/templates/cover-letter-template.dotx— Cover letter reference template. Contains header and styles. This must resolve from career-data, never from the plugin's ownreferences/default — the plugin's copy is the new-user default only (seecareer-engine-setup/SKILL.md), and using it in place of the user's own personalized template was a real production bug (the cover letter export silently ignored the user's actual template every run).$CV_TEMPLATE_HE=${CAREER_DATA}/references/templates/cvHe.dotm— Hebrew CV reference template (note the.dotmextension — this file is macro-enabled, not.dotx).$CL_TEMPLATE_HE=${CAREER_DATA}/references/templates/he-letter.dotx— Hebrew cover letter reference template.$CV_FOOTER=${CAREER_DATA}/references/static-cv-footer.md— the static Education/Languages markdown appended to every English CV before pandoc conversion (see Step 3 below). This must resolve from career-data, never from the plugin's ownskills/career-engine-export/copy — same reasoning as$CL_TEMPLATEabove, and a confirmed real production bug, not a theoretical one:convert-cv.shused to hardcode the plugin's own copy of this file for every CV export, and that plugin-shipped copy had accumulated one real user's actual degree/university content — meaning every installation of this plugin was silently appending someone else's real Education/Languages onto every user's exported CV (fixed 2026-07-09). The plugin's own copy is the new-user blank-{{...}}-placeholder default only (seecareer-engine-setup/SKILL.md).$CV_FOOTER_HE=${CAREER_DATA}/references/static-cv-footer-he.md— the Hebrew-language equivalent, used only for Hebrew CV export (see the Hebrew production protocol below). Same career-data-only resolution rule as$CV_FOOTER.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/assemble_brief_cv.py 24 KB runs code
- scripts/convert-cv.sh 3.8 KB runs code
- scripts/test_assemble_brief_cv.py 10.0 KB runs code
- scripts/test-fixtures/brief-cv-sample.md 1010 B
- scripts/test-fixtures/brief-footer-sample.md 179 B
- scripts/update-subtitle.py 1.1 KB runs code
- static-cv-footer-he.md 504 B
- static-cv-footer.md 378 B
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.
- 8d ago First seen · 545 lines · 55 tokens per session scan A 5c1ed83e233d
career-engine-export is a skill published in the GitHub repository spinningrachel/career-engine (4 stars, last pushed 27d ago), licensed MIT. It adds 55 tokens to every session and 10,325 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.