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 himanshusaleria/gtm-engine --skill analyse-callgit clone --depth 1 https://github.com/himanshusaleria/gtm-engineWrote 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/himanshusaleria/gtm-engine/analyse-call)<a href="https://agentmods.dev/skills/himanshusaleria/gtm-engine/analyse-call"><img src="https://agentmods.dev/badge/skills/himanshusaleria/gtm-engine/analyse-call/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/himanshusaleria/gtm-engine/analyse-call"><img src="https://agentmods.dev/badge/skills/himanshusaleria/gtm-engine/analyse-call.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.00000 | $0.02214 |
| Opus 5 | $0.00000 | $0.01107 |
| Sonnet 5 | $0.00000 | $0.00443 |
| Haiku 4.5 | $0.00000 | $0.00221 |
Grade A, and why
analyse-call 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 8d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analyse-call — Analyse Sales Calls Using Frameworks
Analyse a customer call transcript by applying your sales frameworks. Produces a structured evaluation with coaching insights and next steps.
Usage
/analyse-call {filepath}— Full analysis of a call transcript/analyse-call --quick {filepath}— Summary + next steps only (skip framework breakdown)/analyse-call --scorecard-only {filepath}— Commitment scorecard only/analyse-call --compare {filepath1} {filepath2}— Compare two calls for same prospect
Prerequisites
- At least one framework file exists in
frameworks/ config/config.yamlexists with Linear and team settings
Instructions
When the user invokes /analyse-call, follow these steps:
Step 1: Read the Transcript
Read the call transcript file. Identify:
- Participants — Who from your team, who from the prospect? Use config.team names to identify your team members.
- Company — Which prospect/customer?
- Stage — Where is this deal in the pipeline? (Check Linear {config.linear.pipeline_team} if needed)
- Call type — Discovery, demo, POC review, follow-up, closing?
Step 2: Read the Frameworks
Read all framework files from frameworks/ in the project root.
Available frameworks (read each that exists):
frameworks/customer-profile.md(Customer Profile / ICP)frameworks/market-segments.md(Market Segments / Buyer's Pyramid)frameworks/discovery-questions.md(Discovery Questions / Mom Test)frameworks/intent-signals.md(Intent Signals)frameworks/messaging-structure.md(Messaging Structure)frameworks/pipeline-scorecard.md(Pipeline Scorecard)frameworks/prospect-qualification.md(Prospect Qualification / BANT)frameworks/positioning-levels.md(Positioning Levels / Vitamin vs Painkiller)frameworks/selling-window.md(Selling Window / Org Pain Stages)frameworks/pain-discovery.md(Pain Discovery / SPIN Selling)frameworks/sales-playbook.md(Sales Playbook / 7-Stage Deal Checklist)frameworks/consequence-questions.md(Consequence Questions / Quantified Discovery)frameworks/buyer-readiness.md(Buyer Readiness / Actions vs Words)frameworks/category-language.md(Category Language / Default Filter)frameworks/revenue-visibility.md(Revenue Visibility / Cash-Flow Scoring)
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.
- 8d ago First seen · 221 lines · 0 tokens per session scan A 803a020053df
analyse-call is a skill published in the GitHub repository himanshusaleria/gtm-engine (18 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,214 tokens. 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
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.