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 boshi-xixixi/TraeSkill --skill gtm-board-and-investor-communicationgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/gtm-board-and-investor-communication)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/gtm-board-and-investor-communication"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/gtm-board-and-investor-communication/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/boshi-xixixi/traeskill/gtm-board-and-investor-communication"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/gtm-board-and-investor-communication.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.00077 | $0.04246 |
| Opus 5 | $0.00039 | $0.02123 |
| Sonnet 5 | $0.00015 | $0.00849 |
| Haiku 4.5 | $0.00008 | $0.00425 |
Grade A, and why
gtm-board-and-investor-communication 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- board-and-investor-communication — 94% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Board and Investor Communication
Structure board meetings, investor updates, and executive communication that builds trust and drives decisions — not slide decks that nobody reads.
When to Use
Triggers:
- "How do I prepare for our board meeting?"
- "What should go in our investor update?"
- "We missed our numbers, how do we communicate this?"
- "Board deck structure"
- "How often should we update investors?"
- "Our board meetings aren't productive"
Context:
- Seed through growth-stage companies
- Board meeting preparation and follow-up
- Monthly/quarterly investor updates
- Handling misses and bad news
- Cascading strategy from board to organization
Core Frameworks
1. Tell the Story, Then Show the Data
The Pattern:
Most board meetings start with a data dump. Slide after slide of metrics, then 10 minutes of Q&A where board members try to figure out what it all means.
Flip it. The narrative should lead; data should confirm.
How It Works:
Open with where you are in the journey. Not "here's our ARR" but "here's what we believed coming into the quarter, what we learned, and where that puts us now." Then show the data that validates the narrative.
Board Meeting Structure:
Pre-Read (Sent 48-72 Hours Before)
- Financial dashboard (ARR, burn, runway, pipeline)
- Metric scorecard with health indicators (green/yellow/red)
- 2-3 page narrative summary covering market context and strategic update
- Rule: If it can be read, don't present it
The Meeting (90-120 Minutes)
-
Market context and questions on pre-read (15 min)
- What's changed in the market since last meeting?
- Board asks about anything unclear from pre-read
- No re-presenting the data
-
CEO strategic update — The "Three Things" (15 min)
- What's working (2-3 areas showing momentum)
- What's not (1-2 specific gaps, not vague)
- What we're doing about it (specific changes, not promises)
- This is narrative, not numbers
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 · 457 lines · 77 tokens per session scan A 6db3e16149c2
gtm-board-and-investor-communication is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 4,246 once invoked, about $0.0004 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
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.