Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/LeadMagic/gtm-skillsnpx agentmods add skills/leadmagic/gtm-skills/skills-lockWrote 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/leadmagic/gtm-skills/skills-lock)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/skills-lock"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/skills-lock/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/leadmagic/gtm-skills/skills-lock"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/skills-lock.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.01316 |
| Opus 5 | $0.00026 | $0.00658 |
| Sonnet 5 | $0.00010 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
skills-lock 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 5d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Lock
Overview
Create a deterministic manifest of the skill entrypoints and every packaged support file under skills/. The manifest proves byte-level consistency; it does not certify that content is correct, safe, or trustworthy. Review sources and executable scripts separately.
This repository's schema records both a compatibility-oriented skills index and a complete artifacts index. It does not invent dependency, version, or modification-time fields that cannot be derived reliably from the package.
When to Use
- A skill repository needs a reviewable inventory of everything it ships.
- CI must reject a stale lock after any skill, reference, template, script, or asset changes.
- An installer or reviewer needs to verify a checkout before loading instructions.
- Catalog counts disagree and need one filesystem-derived source of truth.
- The user asks to generate, audit, or explain
skills.lock.
Authoritative Foundations
- Agent Skills specification: keep each skill self-contained and load references, templates, scripts, and assets progressively from the skill directory.
- NIST FIPS 180-4: use SHA-256 as a deterministic digest for the exact bytes in each packaged file.
- Reproducible-build practice: sort paths, exclude volatile metadata from comparisons, and make the same input tree produce the same logical manifest.
Prerequisites
- Identify the repository root and canonical
skills/directory. - Define discoverable skill paths, normally
skills/<category>/<skill>/SKILL.md. - Define explicit exclusions for platform junk and generated caches.
- Confirm whether the task permits writing the lock or only auditing it.
Step-by-Step Process
1. Discover the package from disk
Enumerate skill entrypoints and all regular files beneath skills/. Do not derive counts from README prose, a release description, or a manually maintained catalog.
2. Validate ownership and portability
Ensure every packaged file belongs to one discoverable skill. Reject empty files, cache files, merge residue, unportable symlinks, misplaced artifacts, and non-executable checker scripts.
What ships with it
3 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.
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.
- 5d ago Changed · -151 lines · -31 tokens per session ed5b970356ee
- 9d ago First seen · 280 lines · 83 tokens per session scan A 110590aed6d1
skills-lock is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,316 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-30.
Other skills, from other repositories
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
cialdini-influence
Applies Cialdini's seven principles of ethical persuasion -- Reciprocity, Commitment and Consistency, Social Proof, Authority, Liking, Scarcity, and Unity -- to business contexts including sales, marketing, fundraising, and negotiation. Use when designing conversion funnels, optimizing sales processes, preparing…
competitor-monitoring
Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or…
multichannel-campaign-builder
Use this skill when someone needs a complete outbound sequence written — every touch across LinkedIn and email, not a single cold email. Produces three distinct angles to choose from, then the full sequence with each message ready to send, calibrated to the campaign type and channel mix and self-checked against a…
inbox-digest
Scan the last 48 hours of unread newsletters, news emails, and blog digests. Summarize what's relevant to your work. Trigger when the user asks "what did I miss", "any interesting newsletters", or as part of the morning briefing ritual.
meeting-prep
Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.