Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. 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/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/personalize-message/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote 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/othmane-khadri/yalc-the-gtm-operating-system/personalize-message)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/personalize-message"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/personalize-message/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/othmane-khadri/yalc-the-gtm-operating-system/personalize-message"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/personalize-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 80 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium MCP Rug Pull · line 34 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 81 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00105 | $0.01313 |
| Opus 5 | $0.00053 | $0.00656 |
| Sonnet 5 | $0.00021 | $0.00263 |
| Haiku 4.5 | $0.00011 | $0.00131 |
Grade A, and why
personalize-message 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personalize Message
I'll wrap personalize. I'll ask for the template + target lead, validate inputs, run the CLI, and surface the personalized variant with reasoning so you can approve before sending.
When This Skill Applies
Use this skill when the user says:
- "personalize this message"
- "tailor this outreach to the prospect"
- "rewrite this template for [name]"
- "make this message more personal"
- "generate a personal opener"
NOT this skill (use qualify-leads instead):
- "score these leads" / "qualify these leads" — that runs the 7-gate pipeline, not per-lead copy generation.
NOT this skill (use launch-linkedin-campaign instead):
- "send a LinkedIn outreach to this list" / "start the outbound" — campaign launch handles bulk personalization + sending. This skill is one lead at a time.
NOT this skill (use send-cold-email instead):
- "send this email to [name]" — sending is downstream. This skill produces the variant; you choose where it goes.
What This Skill Does
- Asks for the message template (or accepts pasted text inline) and the target lead (email, linkedin URL, or full record).
- Validates inputs — template non-empty, lead resolvable.
- Shells out to
npx tsx src/cli/index.ts personalize --template <text> --email <email>(or with--linkedin-url,--first-name, etc.). - Parses the CLI output — variant text, reasoning, cost.
- Renders the variant cleanly with a "regenerate?" affordance.
What This Skill Does NOT
- Send the message. That's
send-cold-email(email) orlaunch-linkedin-campaign(LinkedIn) or your manual paste-and-send. - Generate sequences (DM1 + DM2 + follow-ups). That's
launch-linkedin-campaign --variants <n>. - Modify the underlying template or prompt — only the per-lead substitution.
Pre-flight
- Onboarding interruption guard. Run:
Iftest -f ~/.gtm-os/.in-flight-setup && echo "BLOCKED" || echo "OK"BLOCKED, stop and tell the user to finishyalc-gtm startfirst.
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.
- 11d ago First seen · 115 lines · 105 tokens per session scan A aa6274d1819d
personalize-message is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 21d ago), licensed MIT. It adds 105 tokens to every session and 1,313 once invoked, about $0.0005 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 skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.