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/humanizer)<a href="https://agentmods.dev/skills/spinningrachel/career-engine/humanizer"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/humanizer.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.1 | $0.00121 | $0.05232 |
| Opus 5 | $0.00060 | $0.02616 |
| Sonnet 5 | $0.00024 | $0.01046 |
| Haiku 4.5 | $0.00012 | $0.00523 |
Grade A, and why
humanizer 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 7d 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.
⛔ RETIRED FROM ALL PIPELINES (2026-07-26, per the user's direct instruction, 2026-07-26: "The only thing humanizer seems to actually effectively be doing is taking semi and/or non-slop and turning it into its own version of slop. Not helpful. give the gatekeeper the quantitative checks and get rid of humanizer"). The Quantitative Final Gate below now lives in the gatekeeper's Gate 10 (
skills/gatekeeper-checks/letter-gates.md) — that copy is authoritative; this file is history plus explicit user-initiated standalone use only.
Humanizer — Doctrine and Procedure
This is the humanizer agent's complete pattern list and procedure. The agent file (agents/humanizer.md) holds identity, scope, and invocation; this skill holds the mechanics — what to load, what to do, in what order, and the gate that must pass before returning output.
career-data data 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 its career-data discovery preflight and passes into this spawn. Every other file (self-checks, REFERENCES.md, skill docs, default .dotx templates) stays on ${CLAUDE_PLUGIN_ROOT}.
If ${CAREER_DATA} was not provided (direct or standalone invocation), locate the career-data skill yourself, confirm career-data-marker.json, and apply the orchestrator's healthy / damaged / absent outcomes before reading. A configured user's missing career-data is a hard stop — never silently fall back to blank templates.
Output protocol (R-41)
The orchestrator passes the letter at LETTER_PATH (the orchestrator names the file; $PIPE/letter-final.md in the new-application pipeline) — edit it in place (do not return the letter body). Write your change log to $PIPE/humanizer-changes.md.
Return ONLY a 1-line status: Humanized: <n> sentences changed → $PIPE/humanizer-changes.md (or No changes). Edit only the letter file; write only the change-log file. Your entire reply must be exactly that one status line and NOTHING else — no preamble, no analysis, no narration. Do all editing/checking silently; the change-log file is where reasoning belongs, never the reply. Extra prose in the reply is an R-41 violation that re-bloats the orchestrator context this file mechanism exists to keep small.
What ships with it
1 file 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.
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.
- 7d ago First seen · 135 lines · 121 tokens per session scan A 343acae9c873
humanizer is a skill published in the GitHub repository spinningrachel/career-engine (4 stars, last pushed 25d ago), licensed MIT. It adds 121 tokens to every session and 5,232 once invoked, about $0.0006 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…