Borrowing it
Nothing to install: this file belongs to swan-gtm/gtm-skills. 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/swan-gtm/gtm-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/instructions/swan-gtm/gtm-skills/agents-md)<a href="https://agentmods.dev/instructions/swan-gtm/gtm-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/swan-gtm/gtm-skills/agents-md/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/instructions/swan-gtm/gtm-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/swan-gtm/gtm-skills/agents-md.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.02238 | $0.02238 |
| Opus 5 | $0.01119 | $0.01119 |
| Sonnet 5 | $0.00448 | $0.00448 |
| Haiku 4.5 | $0.00224 | $0.00224 |
Grade A, and why
gtm-skills AGENTS.md 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — how to work with this repo
You are an AI agent. This file is written for you. It covers both things a user might ask of you here: installing skills from this library, and submitting a skill to it.
This is the GTM Skills library — open, production-grade go-to-market skills (prospecting, research, outreach, signals, pipeline, RevOps), curated by Swan, served at gtmskills.com and inside the Swan product.
Decide what the user wants
- "Install / use / get skill X" → Installing.
- "Submit / contribute / publish my skill" → Submitting a skill.
- "Update my existing skill / profile" → same as submitting; you edit files under the user's existing
skills/<their-slug>/directory only.
Installing
npx skills add swan-gtm/gtm-skills --skill <skill-name> # one skill
npx skills add swan-gtm/gtm-skills/skills/<creator-slug> # everything from one creator
npx skills add swan-gtm/gtm-skills # whole library, interactive
npx skills add swan-gtm/gtm-skills --list # see what exists
Target a specific agent with -a claude-code, -a cursor, etc. If the user can't run a terminal, fetch the skill folder's raw files from GitHub and place them in the agent's skills directory yourself.
Submitting a skill
The flow: interview → draft → validate → submit. Do the steps in order. A submission is one PR (or one issue) containing one skill.
0. Ground rules (read first)
- You create or edit files only under
skills/<the-user's-author-slug>/. Nothing else, ever. - First submission? That directory won't exist — you'll create it, including
author.md(the user's profile). - The skill folder name is its permanent public identity (installs, URLs). Kebab-case, descriptive, ≤ 60 chars. Check it doesn't already exist anywhere:
ls skills/*/. - Never include any lifecycle/operational field (
prefix,isDefault, anything about auto-install). What ships inside the Swan product is decided by maintainers in their systems, not by this repo. - One level of hierarchy: a skill folder holds
SKILL.mdplus optionalswan.mdandreferences/*.md. No nested skills.
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 · 118 lines · 2,238 tokens per session scan A f5f13aaec11b
gtm-skills AGENTS.md is an instructions file published in the GitHub repository swan-gtm/gtm-skills (148 stars, last pushed yesterday), licensed MIT. It adds 2,238 tokens to every session, about $0.0112 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.