Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add swan-gtm/gtm-skills --skill briefgit 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/skills/swan-gtm/gtm-skills/brief)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/brief"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/brief/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/swan-gtm/gtm-skills/brief"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/brief.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.00041 | $0.00916 |
| Opus 5 | $0.00020 | $0.00458 |
| Sonnet 5 | $0.00008 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
brief 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 9d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
State check. This skill assumes the CRM is connected and holds the deal, company, contact, and engagement history that an exec brief depends on. It also benefits from the org's funnel stages so the brief uses the same language the exec uses. Check the CRM and pull funnel stages. If no CRM is connected, this skill can't produce a real brief — tell the user and stop. If no funnel stages are defined, the brief still works but won't anchor to the org's own pipeline language; recommend defining the funnel.
Step 1 — Pull the canonical state
Anchor on facts, not narrative:
hubspot-search-objectson the company, contacts, and deals — pull deal stage, amount, close date, owner.hubspot-get-engagementsto read the last 5-10 substantive touchpoints (meetings + calls only, skip routine emails).swan-search-companiesfor the company's Swan record — target-market fit, tags, funnel stage.swan-search-sequencesto know what outreach has run and how it performed.
If the engagement history is dense, read the full JSON from files/tool-outputs/hubspot-get-engagements_<callId>.json in swan-execute-code and print only meetings + call notes — drop routine emails.
Step 2 — Map the buying committee
For multi-threaded enterprise accounts, name the committee:
- Economic buyer, champion, technical evaluator, blocker, end users.
- For each: name, title, last engagement, sentiment in one word (engaged, neutral, cold, hostile).
Pull from contact records + meeting notes. Don't invent sentiment — quote what they actually said when possible.
Step 3 — Identify the risks
The exec wants to know what kills the deal. Surface three to five risks max, each one specific:
- Stakeholder risk: a key buyer hasn't engaged, the champion is leaving.
- Commercial risk: budget, timing, procurement, legal blockers raised in calls.
- Competitive risk: a competitor is in evaluation, an incumbent contract renewal date.
- Execution risk: technical scoping incomplete, integrations unknown, security review pending.
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.
- 9d ago First seen · 85 lines · 41 tokens per session scan A 911a0814d7f5
brief is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 916 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.