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 bridgebound-history-16git 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/bridgebound-history-16)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/bridgebound-history-16"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/bridgebound-history-16/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/bridgebound-history-16"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/bridgebound-history-16.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.00059 | $0.00719 |
| Opus 5 | $0.00030 | $0.00360 |
| Sonnet 5 | $0.00012 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
bridgebound-history-16 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 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.
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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BRIDGEBOUND Category II: Based on History (16 Triggers)
Demo Pipeline (3 Triggers)
- Requested a Demo But Didn't Schedule One - Demo request abandonment
- Agreed to a Demo & No-Showed - No-show follow-up
- Prospects Who "Abandoned the Chat" - Chat abandonment
Closed-Lost (5 Triggers)
- Demoed in the Past (Ghosted or Went Dark) - Ghosted prospects
- Went with a Competitor & Up on Renewal - Competitor renewal timing
- You Messed Up (Ex. Objection of No Budget) - Past objection resolution
- Didn't Hit ICC (Size) - Company grew into ICP
- Didn't Hit ICC (Criteria that DQs) - Criteria changed
Executive Churn / UserGems (3 Triggers)
- Customers Who Went to Another Company - Champion tracking
- Customers Who Changed Roles Internally - Internal moves
- Prospective Company New Hires, Who Never Used Your Product - New decision makers
Email Engagement (3 Triggers)
- Opened Prospecting Emails - Email openers
- Opened Prospecting Emails (Aggressively) - Multiple opens
- Received an OOO to Prospecting Emails - OOO responses (timing intel)
Reciprocity (2 Triggers)
- Companies that Sold You THEIR Product (Tit for Tat) - Vendor relationships
- Competitors of Your Current Customers - Competitive intelligence
Re-Engagement Template
Subject: since we last talked
{{firstName}},
When we talked in {{month}}, you mentioned {{objection}}.
Since then, we've {{improvement}}.
Worth another look?
Timing Considerations
| Trigger Type | Optimal Timing |
|---|---|
| No-show | Same day + 2 days later |
| Ghosted | 30-60 days later |
| Competitor renewal | 90 days before renewal |
| Champion job change | Days 14-45 in new role |
Combines with
| Skill | Why |
|---|---|
cold-email-templates-34 |
Re-engagement templates (#31-34) |
buying-signals-6 |
Champion tracking (signal #1) |
clay-enrichment-9step |
Track job changes in Clay |
cold-call-scripts |
No-show phone script |
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 · 105 lines · 59 tokens per session scan A d440b8b6fbcb
bridgebound-history-16 is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 719 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
signals-hooks
Comprehensive reactive state hooks for integration with flutterhooks.
signals-dart
Advanced reactive state primitives, collections, mixins, and utilities of signalscore.
signals-flutter
Highly optimized Flutter UI bindings and GPU rendering for reactive signals.
signals-migration-6-to-7
Detailed guidelines, patterns, and rules for migrating codebases from signals.dart version 6.x to version 7.x.
signals-preact-dart
Core reactive programming best practices and primitive definitions for preactsignals in Dart.
signals-lint
Standardized compiler diagnostics, static analysis lints, and automated IDE quick-fixes.