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 one-pagergit 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/one-pager)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/one-pager"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/one-pager/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/one-pager"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/one-pager.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.00022 | $0.02625 |
| Opus 5 | $0.00011 | $0.01313 |
| Sonnet 5 | $0.00004 | $0.00525 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
one-pager 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One-Pager
Single-page enablement documents that communicate a product, feature, solution, event, insight, or competitive comparison in a format scannable in 30 seconds. Three-phase process: design the wireframe layout, fill with structured content, then polish the copy.
The body of this file holds decision-grade context (when to invoke, inputs, type-selection table, anti-hallucination guardrails, gotchas, integration). Step-by-step process, output template + worked example, quality gates, and DESIGN.md integration spec live in the premium reference.
Doctrine inherited (Step 7 — 0626 rollout)
Output complies with:
output-tenets.md— the seven tenetsoutput-simplicity.md— length caps, three-layer source placement, robot-tells bandoc-output-structure.md— GDoc/Notion structural defaults- Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]]
Refinements applied to this skill:
| Code | Refinement | How it lands in one-pager |
|---|---|---|
| R1 | Source placement (three layers) | One-pagers are end-customer-facing (leave-behinds, exec briefs). No sources block. Citations stay in working markdown for QA review only; stripped before publish. The page IS the doc. |
| R3 | Product-update tone | Product overview / feature spotlight / solution brief variants frame as "we shipped X" not "we are thrilled to announce." Even Tier 1 launches. |
| R6 | CTA hierarchy | Market-facing variants (product overview, feature spotlight, solution brief) → sign-up primary, blog/longer-read as fallback. Warm-base variants (event recap, insight summary) → product-action CTA. Never both. |
| R8 | Entity-name headings | When the one-pager features a specific product/feature/event, headings repeat the entity name ("What [Product] does," "Who [Product] is for," "How [Product] is different") — not pronoun headings ("What it does"). |
| R9 | Action-oriented section names | Use "How to sign up to [Product]" instead of "What happens next." "The problem we're solving" instead of "The problem we built for." Action over status. |
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 · 219 lines · 186 tokens per session scan A 7d7e9fc9dfea
one-pager is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,625 once invoked, about $0.0001 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.
ui-ux-gtm
Design GTM UI/UX patterns — landing pages (hero, proof, CTA), forms (progressive disclosure, inline validation), signup flows (activation, time-to-value), dashboards (KPI hierarchy, trend indicators), and accessibility (WCAG 2.2 AA). Use when designing or auditing GTM tool interfaces, landing pages, conversion flows…
design-system-gtm
Define brand-context for AI agents — visual identity systems, voice/tone guides, color palettes with hex/RGB/HSL, typography systems with font stacks and type scales, logo usage rules, asset templates, and brand guardrails. Use when creating a design system for AI-generated GTM content, ensuring brand consistency…
graphic-design-gtm
Create GTM visual assets — social graphics, ad creatives, pitch deck design, one-pager layouts, email images, data visualization, and brand-consistent templates. Use when creating visual content for GTM, designing social media graphics, building ad creatives, or establishing visual identity for campaigns. Triggers on…