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/integrate-with-yalc/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/integrate-with-yalc)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/integrate-with-yalc"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/integrate-with-yalc/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/integrate-with-yalc"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/integrate-with-yalc.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.00138 | $0.03060 |
| Opus 5 | $0.00069 | $0.01530 |
| Sonnet 5 | $0.00028 | $0.00612 |
| Haiku 4.5 | $0.00014 | $0.00306 |
Grade C, and why
integrate-with-yalc scanned grade C with 3 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
2. **Collision detection is probabilistic, not deterministic.** Never tell the user a collision is "resolved" — always instruct them to test empirically. The table flags risk; it doesn't prove runtime behaviour. Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find "<user-repo-path>/.claude/rules" -name "*.md" 2>/dev/null | xargs cat Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
find "<user-repo-path>/.claude/skills" -name "SKILL.md" 2>/dev/null | sort | xargs -I{} sh -c 'echo "=== {} ===" && head -40 {}' How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate with YALC
The user has an existing Claude Code repo — their own skills, CLAUDE.md, project rules — and wants to run it alongside YALC without breaking either. This skill reads both sides, flags every conflict, and produces a written integration plan the user can review before anything changes.
Read-only by default. Nothing is moved or written until the user explicitly confirms the apply step.
When This Skill Applies
- "integrate my repo with YALC"
- "I have my own Claude Code setup, how do I add YALC"
- "merge my repo with YALC"
- "how do I bolt YALC onto my existing skills"
- "I want to use my own skills alongside YALC"
- "I already have a
.claude/folder — can I still use YALC?"
NOT this skill (use icp-import instead):
- User just wants to import their ICP/voice/context — no skills to reconcile.
NOT this skill (use yalc-orientation instead):
- User is new to YALC and has no existing repo to integrate.
Inputs
Ask for both in a single message if not provided:
- Absolute path to your existing repo (e.g.
/Users/alice/my-claude-setup) — the root directory where your.claude/folder lives.- One-line description of what your repo does (optional but useful — e.g. "agency operations brain for B2B SaaS GTM").
If the user already provided the path in their message, use it directly. Don't ask for it again.
Procedure
Step 0 — Validate inputs
Confirm the path exists and contains a .claude/ directory:
test -d "<user-repo-path>/.claude" && echo "OK" || echo "MISSING"
If MISSING: tell the user the path doesn't look like a Claude Code repo (no .claude/ folder found) and ask them to double-check.
Step 1 — Read the user repo (read-only)
Collect the following. If any are absent, note it but continue — absence is informative.
a) Directory tree (top two levels):
find "<user-repo-path>" -maxdepth 2 -not -path '*/.git/*' | sort
b) All skill names + descriptions + trigger phrases:
find "<user-repo-path>/.claude/skills" -name "SKILL.md" 2>/dev/null | sort | xargs -I{} sh -c 'echo "=== {} ===" && head -40 {}'
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 · 240 lines · 138 tokens per session scan C cd4f0c311f6f
integrate-with-yalc is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 23d ago), licensed MIT. It adds 138 tokens to every session and 3,060 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 3 findings (subtle steering, reads agent configuration directories, enumerates other installed skills). 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-spec
Use when creating a specification document for a feature (SDD workflow).
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-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-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.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.