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 context-setupgit 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/context-setup)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/context-setup"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/context-setup/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/context-setup"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/context-setup.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.00223 | $0.02574 |
| Opus 5 | $0.00112 | $0.01287 |
| Sonnet 5 | $0.00045 | $0.00515 |
| Haiku 4.5 | $0.00022 | $0.00257 |
Grade A, and why
context-setup 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/context-setup — Orchestrate a client context engagement
Situation. Genesys sells "build your context layer" as a Lane-3 engagement — the £9-10.8K/mo AI-transformation build. It's live at ClientCo and in-flight at ClientCo.
Complication. The mechanics are ad-hoc. /new-client scaffolds Pattern A folders and prompts the spine chain but doesn't drive it. Nothing locks the sequence, so a downstream skill can run before its upstream is canonical. And the per-client context repo — the thing the client's team actually runs against, like ClientCo-marketing — is hand-built each time.
Question. What makes this build repeatable and sellable instead of a bespoke rebuild every engagement?
Answer. This skill. It does two jobs, in order: (1) drive the context spine as a locked, dependency-gated sequence — build the brain before any engine — and (2) generate the per-client context repo from the locked spine, ready for its own GitHub remote.
This is an orchestration runbook — it coordinates other skills and emits a repo. It does not itself produce a spine artifact; each spine skill does that.
The methodology adapts patterns surfaced in the /steal analysis at ../../../../discovery/0726-jacob-dietle-context-os-steal-analysis.md (cite-only — the source author is a tracked Genesys competitor; adapt the ideas, never reproduce his brand terms).
When to run
Invoke when:
- "build the context OS for {client}"
- "stand up {client}'s context repo"
- "run the Lane-3 context build for {client}"
- starting a paid AI-transformation engagement where the deliverable is a client's owned context system
Do NOT invoke when:
- The user only wants the empty folder scaffold → use
/new-client. - The user wants existing global skills packaged into a distributable bundle → use
/plugin-scaffold. - The user wants a single spine artifact (just positioning, just messaging) → run that skill directly.
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 · 167 lines · 223 tokens per session scan A 5f9291a21bd9
context-setup is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 223 tokens to every session and 2,574 once invoked, about $0.0011 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
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.…
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.
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.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
add-editor
Wire Deus's memory + evolution layers into an external code editor (Zed and other ACP/MCP clients) so the editor's own agent gains Deus's vault recall and self-improving reflexion loop. Configuration only — no new code. Triggers on "add editor", "use Deus in my editor", "zed integration", "editor integration", "wire…
resume
Load context from permanent memory and recent session logs. Tiered loading — CLAUDE.md full, session logs frontmatter-only by default.