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 wikigit 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/wiki)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/wiki"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/wiki/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/wiki"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/wiki.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.00129 | $0.02641 |
| Opus 5 | $0.00064 | $0.01321 |
| Sonnet 5 | $0.00026 | $0.00528 |
| Haiku 4.5 | $0.00013 | $0.00264 |
Grade A, and why
wiki 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 11d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wiki — per-client-folder hygiene and drift detection
Runs inside a single client engagement folder. Catches semantic drift, stale references, and structural gaps before they contaminate a deliverable.
/audit covers the whole workspace. /workspace-cleanup covers file-system hygiene globally. /wiki covers content consistency inside one client folder — which neither of the other two can do.
Triggers
Invoke when user says:
/wiki(run lint against the current client folder, auto-detected from cwd)/wiki lint {client-slug}— run lint against a specific active client/wiki status— show which clients are missing hot.md / log.md/wiki status {client-slug}— show hot.md + last 10 log.md entries for a client- "lint this client folder"
- "check this engagement for drift"
- "what's stale in {client}?"
Do NOT invoke when:
- User wants to clean up the global workspace (use
/workspace-cleanup) - User wants a full workspace health audit (use
/audit) - User wants to absorb new source material (use
/learn) - User wants to run structured research (use
/company-context,/competitor-research, etc.)
Subcommands
| Command | Action |
|---|---|
/wiki |
Lint the current client folder (auto-detect from cwd) |
/wiki lint {client-slug} |
Lint a specific active client |
/wiki status |
Show which clients have complete operations layer (CLAUDE.md + hot.md + log.md) |
/wiki status {client-slug} |
Show the current hot.md + recent log.md for one client |
/wiki history {client-slug} |
Parse log.md and show the full operation timeline |
Parse $ARGUMENTS to route. Default (no args) = lint current folder.
Subcommand: status (no client)
Walk projects/consulting/active/*/ and report which clients have the full operations layer:
| Client | CLAUDE.md | hot.md | log.md | Last log entry |
|---|---|---|---|---|
| ClientCo | ✓ | ✓ | ✓ | 2026-04-11 init |
| ClientCo | ✓ | ✓ | ✓ | 2026-04-11 init |
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.
- 11d ago First seen · 276 lines · 129 tokens per session scan A d38cedc56244
wiki is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,641 once invoked, about $0.0006 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.…
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.