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 tutur3u/platform --skill tuturuuu-cms-studiogit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/tuturuuu-cms-studio)<a href="https://agentmods.dev/skills/tutur3u/platform/tuturuuu-cms-studio"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-cms-studio/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/tutur3u/platform/tuturuuu-cms-studio"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-cms-studio.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.00025 | $0.01086 |
| Opus 5 | $0.00013 | $0.00543 |
| Sonnet 5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
tuturuuu-cms-studio 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuturuuu CMS Studio
Core Workflow
Use this skill for apps/cms and external-project content work, especially when
the request is about making content editing easier for non-technical users.
Start with the repo AGENTS.md, git status --short, and active
tmp/agent-coordination/ notes. Keep sibling branded sites as read-only context
unless the task explicitly needs integration changes there.
Discovery
Map the CMS control plane before editing:
apps/cms/src/features/cms-studio/for editor shells, content model, capability grouping, media, workflow, preview, and entry detail behavior.apps/cms/src/features/home/for the operator landing page.apps/cms/src/app/[locale]/(dashboard)/[wsId]/navigation.tsxandcms-paths.tsfor new CMS routes and aliases.apps/cms/src/lib/external-projects/access.tsfor CMS workspace gates and satellite app-session access.- sibling
lib/*-external-project-manifest.tsfiles only to understand collection slugs, profile fields, blocks, and assets consumed by each branded site.
Prefer improving the centralized CMS experience over adding new bespoke admin UI inside each sibling site.
Default new CMS-backed websites to the cms_site v1 contract. Keep site-specific
fields, groups, and delivery hints in template and collection schema/profile
metadata. Add a dedicated adapter only when the remote system has a genuinely
different protocol or authentication model. Existing branded adapters remain
compatibility paths, not templates for new work.
UX Rules
- Make the default path task-based: landing-page edits, content library, preview, and member access should be obvious without knowing CMS internals.
- Keep visible CMS product copy on consumer vocabulary: site, site template, connection, content, section, URL path, custom details, media, publishing, preview, people, invitations, and team access. Do not expose external project, canonical, adapter, binding, slug, schema, metadata, profile data, payload, or JSON in normal editor paths.
- Treat landing-page content as first-class for branded projects. Group hero, profile, section, featured, navigation, and primary-link collections behind a simple "Landing page" surface when possible.
- Keep Landing, Library, and Games scopes distinct. Landing is a page-builder for landing-only sections and readiness checks; Library is content operations for non-landing/non-game content; Games remains the playable-project surface behind the CMS Games flag. Add capability tests whenever collection grouping changes.
- CMS team access must use external-project-aware
apps/webroutes and@tuturuuu/internal-apihelpers. Do not call the standard workspace members or roles settings endpoints directly fromapps/cms; those routes can 403 for app-session users who are valid CMS editors. - Keep raw configuration, implementation IDs, site-type mappings, and workflow mechanics out of the primary editor path unless the user is doing advanced configuration. Put exact implementation values behind collapsed Developer details panels or internal root-console advanced controls.
- Use explicit empty, loading, error, and review states that tell editors what to do next.
- Add, remove, or replace CMS translation keys with
bun i18n:add --app cmsand--mode add|remove|replace; use--entriesor--entries-filefor bulk updates so every detected locale file is updated and sorted together. Reserve manual message JSON edits for broad prose rewrites or value-only updates, then runbun i18n:sort. - Maintain the CMS product-copy hygiene test when adding CMS-owned strings. Add narrow exceptions only for admin/developer-detail surfaces that genuinely need exact implementation values.
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.
- 10d ago Changed · -26 tokens per session ff652a5f1565
- 13d ago First seen · 103 lines · 51 tokens per session scan A fed532de0c9e
tuturuuu-cms-studio is a skill published in the GitHub repository tutur3u/platform (53 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 1,086 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
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
frontend-engineer
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults" !cat .forgewright/codebase-context.md…
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.