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 Gekkos-tech/agency-os --skill cms-integrationgit clone --depth 1 https://github.com/Gekkos-tech/agency-osWrote 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/gekkos-tech/agency-os/cms-integration)<a href="https://agentmods.dev/skills/gekkos-tech/agency-os/cms-integration"><img src="https://agentmods.dev/badge/skills/gekkos-tech/agency-os/cms-integration/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/gekkos-tech/agency-os/cms-integration"><img src="https://agentmods.dev/badge/skills/gekkos-tech/agency-os/cms-integration.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.00179 | $0.00983 |
| Opus 5 | $0.00089 | $0.00491 |
| Sonnet 5 | $0.00036 | $0.00197 |
| Haiku 4.5 | $0.00018 | $0.00098 |
Grade A, and why
cms-integration 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CMS Integration
Most client sites need SOME editable content — and most agencies either over-engineer (full CMS for two text fields) or under-engineer (client calls you for every typo). This skill picks the right tier and integrates it without breaking the design handoff.
Step 1 — Establish what actually needs editing
Before naming any system, list the editable surfaces from the brief/concept:
- Which content changes, how often, and by whom? (opening hours weekly ≠ legal pages yearly)
- Structured data (menu items, team members, jobs) or free-form pages?
- Does the client add PAGES, or only edit content within existing ones?
- Media uploads? Multilingual? Scheduled publishing? Multiple editors/roles?
If the honest answer is "a phone number and opening hours twice a year" — recommend no CMS: keep content in typed config/content files, offer a maintenance retainer instead. Say this explicitly; it's often the right call.
Step 2 — Decision tree
| Situation | Recommendation |
|---|---|
| Few fields, rare edits, technical-ish client | No CMS (content files + retainer) |
| Git-based site, budget-sensitive, simple editing | Decap CMS (free, edits commit to the repo) |
| Next.js project, client edits structured content, self-hosted preferred | Payload (TypeScript-native, lives in the repo, DSGVO-friendly self-hosting) |
| Content-heavy, multiple editors, real-time collaboration, budget exists | Sanity (hosted, excellent editor UX, GROQ) |
| Marketing team edits page LAYOUTS (visual composition), multi-language | Storyblok (visual editor, EU-hosted option) |
| Client insists on the WordPress admin they know / migration from WP | Headless WordPress (WP admin + REST/WPGraphQL, frontend stays yours) |
| Self-hosted requirement + non-JS backend team | Strapi |
DACH note: for DSGVO-sensitive clients, prefer self-hosted (Payload, Strapi,
Decap, WP on German hosting) or EU-region SaaS (Storyblok EU, Sanity EU
dataset) — and record the choice + data location in the privacy policy via
pre-launch-checklist.
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.
- 9d ago First seen · 69 lines · 179 tokens per session scan A bab605bb57d5
cms-integration is a skill published in the GitHub repository Gekkos-tech/agency-os (5 stars, last pushed 1mo ago), licensed MIT. It adds 179 tokens to every session and 983 once invoked, about $0.0009 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-31.
Other skills, from other repositories
telegram
Send Telegram messages, files, and alerts via bot API; read replies; ask questions with inline buttons and wait for the answer (approve-from-phone). Supports multiple bots and named chat targets. Use when the user wants to send a Telegram message or alert, get notified on Telegram when a task finishes or needs input…
insforge-cli
Use this skill whenever someone needs a backend, or a task touches InsForge backend or cloud infrastructure through the InsForge CLI: projects, SQL, migrations, RLS policies, functions, storage, backups, deployments, compute, secrets, config, schedules, logs, diagnostics, advisor scans and suppressions, import/export…
insforge
Use this skill when writing app code with InsForge or @insforge/sdk: database CRUD, auth, storage uploads/storage RLS, functions, OpenRouter AI, realtime, emails, Stripe or Razorpay payments, or pointing S3-compatible tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) at InsForge Storage. Trigger on requests like…
insforge-debug
Use when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denial, realtime channel issues, slow query on one endpoint, edge function or Vercel deploy failure), proactive audits…
yolo
Automation skill for Lovable deployments. Activates when: yolomode: on in CLAUDE.md Running /deploy-edge or /apply-migration commands After git push when autodeploy: on (automatic detection) Any mention of "yolo mode", "automate Lovable", "browser automation", "Lovable MCP" Uses Lovable MCP (preferred) or browser…
telegram-dev
A development guide for Telegram, a messaging platform, covering bots, web apps that run inside Telegram, and client applications. It includes messaging, payments, login, webhooks, storage, and sensor-related interfaces.