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 lumenharbor/garchi-cms-skills --skill garchi-manage-contentgit clone --depth 1 https://github.com/lumenharbor/garchi-cms-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/lumenharbor/garchi-cms-skills/garchi-manage-content)<a href="https://agentmods.dev/skills/lumenharbor/garchi-cms-skills/garchi-manage-content"><img src="https://agentmods.dev/badge/skills/lumenharbor/garchi-cms-skills/garchi-manage-content/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/lumenharbor/garchi-cms-skills/garchi-manage-content"><img src="https://agentmods.dev/badge/skills/lumenharbor/garchi-cms-skills/garchi-manage-content.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.00113 | $0.03249 |
| Opus 5 | $0.00056 | $0.01625 |
| Sonnet 5 | $0.00023 | $0.00650 |
| Haiku 4.5 | $0.00011 | $0.00325 |
Grade A, and why
garchi-manage-content 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 4d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Garchi CMS: operating content over MCP
Content lives in the CMS. If the user wants different copy, a new page, a new blog post or a different image, that is an MCP operation and the application code should not change at all.
Requires the garchi MCP server. If its tools are unavailable, stop and ask the
user to authorize it. Do not substitute source edits for CMS edits.
Start every session by calling get-garchi-cms-guide. It is free,
read-only, takes no arguments, and returns the current content model and field
rules straight from the server. It is more current than this file. Read it
before planning any write.
The one thing to understand: ids flow between calls
Almost every Garchi tool takes an id that a previous call returned. Nothing is derivable, nothing is guessable. Most failed Garchi sessions are an agent inventing an id instead of listing for it.
list-space-tool ─────────► space_uid ──► needed by nearly every other tool
│
┌────────────────────────┼────────────────────────┐
▼ ▼ ▼
list-section-template list-pages-tool list-categories-tool
│ │ │
│ section_template_id │ page_id │ category ids
│ + prop template ids │ │
▼ ▼ ▼
create-section-tool ──► get-page-tool ──► section ids create-data-item-tool
│ (mode=draft) │ │
└──────────┬──────────────────────────────┘ ▼
▼ create-meta-for-item
upsert-section-content-tool
(needs page_id + section_id + prop template ids)
Two id traps worth knowing:
get-page-tooltakes aslug(/,/about), not a page id. Butupsert-section-content-tool,delete-section-tooland the rank tools take apage_id. Get the id fromlist-pages-tooland the section ids fromget-page-tool.get-data-item-tool,update-data-item-toolandcreate-meta-for-item-tooltake a numericitem_id, not the slug.
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.
- 4d ago Changed · +6 lines 7963255cc7f0
- 11d ago First seen · 253 lines · 113 tokens per session scan A e3359f016001
garchi-manage-content is a skill published in the GitHub repository lumenharbor/garchi-cms-skills (0 stars, last pushed 5d ago), licensed MIT. It adds 113 tokens to every session and 3,249 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…