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 Mora-AI-Content-Studio/mora-claude-plugin --skill content-gap-checkgit clone --depth 1 https://github.com/Mora-AI-Content-Studio/mora-claude-pluginWrote 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/mora-ai-content-studio/mora-claude-plugin/content-gap-check)<a href="https://agentmods.dev/skills/mora-ai-content-studio/mora-claude-plugin/content-gap-check"><img src="https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/content-gap-check/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/mora-ai-content-studio/mora-claude-plugin/content-gap-check"><img src="https://agentmods.dev/badge/skills/mora-ai-content-studio/mora-claude-plugin/content-gap-check.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.00087 | $0.00626 |
| Opus 5 | $0.00044 | $0.00313 |
| Sonnet 5 | $0.00017 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
content-gap-check 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Gap Check
Compare what a Mora account has planned against what has actually been posted, and surface the difference. This is a distinct question from performance (content-performance-audit) or brand facts (brand-brief): it's about execution against a plan, not quality or identity.
Scope
This is a question about execution against a plan, not about quality or identity. Route performance questions ("what's working") to content-performance-audit and brand questions ("what do we sell") to brand-brief instead of this skill.
Procedure
- Call
list_projectsto get this account's content projects, each with itsslots(fromproject_tasks:topic,cta,platform,scheduled_at,status). - Call
list_posts(no status filter, or a generous limit) to get the account's actual posts across all statuses. - Compare, per project:
- Overdue — a slot with
scheduled_atin the past whosestatusis not a terminal completed state, and with no obviously matching post inlist_posts(match loosely on platform + rough timing + topic language; do not claim a definitive 1:1 match the data can't support — say "likely matches" or "no clear match" rather than asserting certainty). - On track — slots with a scheduled date still ahead, or a status indicating completion.
- Orphan posts — published or scheduled posts in
list_poststhat don't correspond to any planned slot. This is not necessarily a problem (spontaneous posts are normal) but is worth naming if the user is asking specifically about plan adherence.
- Overdue — a slot with
- Report gaps plainly, grouped by project: what's overdue, what's on track, and what's
unaccounted for. Do not soften an overdue slot into "on track" language, and do not treat a
slot's mere existence as proof it was executed — only
list_postsevidence counts as execution.
Honest emptiness
If list_projects returns zero projects, say this account has no content projects in Mora —
that's a statement about planning, not about the business having no content strategy. If
list_posts returns zero posts while projects exist, say the plan has no matching execution
yet rather than guessing at reasons. Never infer that a gap was intentional (e.g. "they must
have decided to skip this") — report the gap and let the user explain it.
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 · 45 lines · 87 tokens per session scan A 081b9f3ebec1
content-gap-check is a skill published in the GitHub repository Mora-AI-Content-Studio/mora-claude-plugin (0 stars, last pushed 19d ago), licensed MIT. It adds 87 tokens to every session and 626 once invoked, about $0.0004 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…