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 pipeline-reviewgit 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/pipeline-review)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/pipeline-review"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/pipeline-review/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/pipeline-review"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/pipeline-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium Rogue Agent · line 72 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 Rogue Agent · line 75 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 Excessive Agency · line 77 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00034 | $0.01179 |
| Opus 5 | $0.00017 | $0.00589 |
| Sonnet 5 | $0.00007 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
pipeline-review 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
Setup state. Not yet configured for this org. Load the Setup sub-page and walk the user through mapping their CRM stages to the Swan funnel model, recording per-stage SLAs, and setting the review cadence before running a review. (After setup is performed, rewrite this paragraph via swan-update-skill to describe the current state — funnel stages mapped from CRM, required field mappings, per-stage SLAs in days, review cadence and delivery channel, and last-refreshed date — so future runs see the current configuration without re-checking.)
What this skill does
Walk the user's pipeline. Surface deals that need attention: stalled in stage, regressed in stage, missing key activities, or showing risk signals. Output: a short prioritized list with one action per item. Not a forecast — that's a separate verb.
Step 1 — Scope the review
Ask once:
- Whose pipeline (a specific AE, a team, the whole org)?
- Which stages (mid-funnel only by default — exclude early discovery and closed)?
- Time horizon (default: deals expected to close this quarter, plus anything aging > 30 days regardless of close date).
If the user hasn't said which AE, default to all open mid-funnel deals.
Step 2 — Pull the deal slice
hubspot-search-objects (object: deals) filtered to the chosen owner(s), open stages, and the date window. Page size 20. Pull associated company and amount.
If the result is > 40 deals, switch to swan-execute-code: dump the deals query result and aggregate from disk.
Step 3 — Flag anomalies per deal
For each deal in the slice, check three things (cheap, no enrichment):
| Flag | Check | How |
|---|---|---|
| Stalled | No engagement / activity update > 21 days | Deal hs_lastmodifieddate > 21 days ago |
| Regressed | Stage went backwards | Check stage history if available; or compare to prior pipeline snapshot in memory |
| Risk: low engagement | < 3 distinct contacts engaged in last 30 days | hubspot-get-engagements on the deal — count distinct contacts |
| Risk: champion gone | Primary contact left the company | swan-search-companies for the contact's current company vs deal company |
| Risk: amount missing | Deal in late stage with no amount | Deal amount field empty + stage past discovery |
| Risk: close date stale | Close date in the past or > 90 days out for a "this quarter" deal | Compare to today |
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.
- 9d ago First seen · 110 lines · 34 tokens per session scan A 0ba1482c4f6c
pipeline-review is a skill published in the GitHub repository swan-gtm/gtm-skills (153 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,179 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
Pipedrive Automation
Automate Pipedrive CRM workflows including deal management, pipeline tracking, and sales reporting.
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…
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.