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 matteotitta/genesys-skills --skill technographics-from-websitegit clone --depth 1 https://github.com/matteotitta/genesys-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/matteotitta/genesys-skills/technographics-from-website)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/technographics-from-website"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/technographics-from-website/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/matteotitta/genesys-skills/technographics-from-website"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/technographics-from-website.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.00007 | $0.02607 |
| Opus 5 | $0.00003 | $0.01303 |
| Sonnet 5 | $0.00001 | $0.00521 |
| Haiku 4.5 | $0.00001 | $0.00261 |
Grade A, and why
technographics-from-website 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/technographics-from-website — Detect vendor usage from a lead's website
Find out which back-office system, CRM, or platform a lead uses by analysing their public website. Visual extraction is the primary signal (screenshots fed to vision model identify login button labels, footer logos, embedded widget branding, "powered by" mentions). HTTP-probe verification is the optional confidence booster where the vendor has a discoverable portal subdomain pattern (e.g., *.mypfp.co.uk for ClientCo Personal Finance Portal).
Vendor-agnostic at the skill layer. Per-vendor profiles live in the premium reference and define the visual tells, optional HTTP verifier, and outbound-copy hook templates for each vendor universe.
Research stack (Exa): primary tools web_fetch_exa, web_search_exa for customer-list discovery. Chrome DevTools MCP for screenshot capture. Firecrawl as fallback. All per .claude/rules/exa-protocol.md.
Imported via: /steal analysis 2026-05-18 (.claude/discovery/0526-ClientCo-pfp-fingerprint-steal-analysis.md) — abstracted from the ClientCo PFP HTTP-probe technique into a vendor-agnostic visual + verifier skill.
When to use this vs. other skills — voice-locked routing
| Skill | Question it answers |
|---|---|
/clay-search or /build-tam |
Who should we target? (People discovery) |
/deepline-enrich |
How do we reach them? (Emails, phones) |
/niche-signal-discovery |
When should we reach out? (Timing + intent) |
/lead-scoring |
How ready are they? (Qualification + prioritisation) |
/technographics-from-website |
Which vendor do they use? (Technographic signal) |
/company-context |
Who are they? (Firmographics + traction) |
/outreach-emails |
What do we say? (Personalised sequences) |
Handoff pattern: /clay-search or /build-tam (lead list) → /technographics-from-website (vendor signal overlay) → /lead-scoring (consume signal as technographic dimension) → /outreach-emails (use vendor-specific copy hook).
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 · 191 lines · 227 tokens per session scan A 1cdda2d568ff
technographics-from-website is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 2,607 once invoked, about $0.0000 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
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.