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 agentmods add skills/clever-cc-plugins/cc-content/new-content-skillnpx skills add clever-cc-plugins/cc-content --skill new-content-skillgit clone --depth 1 https://github.com/clever-cc-plugins/cc-contentWrote 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/clever-cc-plugins/cc-content/new-content-skill)<a href="https://agentmods.dev/skills/clever-cc-plugins/cc-content/new-content-skill"><img src="https://agentmods.dev/badge/skills/clever-cc-plugins/cc-content/new-content-skill.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.05590 |
| Opus 5 | $0.00032 | $0.02795 |
| Sonnet 5 | $0.00013 | $0.01118 |
| Haiku 4.5 | $0.00006 | $0.00559 |
Grade B, and why
new-content-skill scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skill-drafts/<format-name>/ 2>/dev/null && echo "found" || echo "missing" How it starts
The opening of the file, as written. The whole thing — 509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Content Skill
This meta-skill turns external research reports into a fully structured content-production
skill. It reads research files from the staging folder, assesses coverage across all content
axes, synthesizes a three-layer format-guidelines.md, and generates a SKILL.md skeleton
ready for customization.
Step 0: Recall learnings
If .claude/learnings.md exists, read it silently. Apply relevant entries — such as
prior skill-creation observations or project-level defaults that would affect how this
skill is structured. Do not announce this step. If the file is absent, continue normally.
Step 1: Determine the format name and mode
If the user passed a format name as $ARGUMENTS, use it. Normalize to kebab-case
(e.g., "Blog Article" → blog-article, "Marketing Email" → marketing-email).
Strip the --plugin flag from $ARGUMENTS before deriving the format name — it is not
part of the name.
If no argument was passed, ask:
"What content format is this skill for? Provide a short kebab-case name — for example:
blog-article,marketing-email,whitepaper,video-script,case-study."
Wait for the answer before proceeding.
Determine the mode. After resolving the format name, check whether $ARGUMENTS
contains the flag --plugin.
-
If
--pluginis present: you are in plugin-dev mode. The output will go into thecc-contentplugin repository atplugins/cc-content/skills/<format-name>/. -
If
--pluginis absent: ask once:"Where should this skill be created? Reply
projectfor a project-local custom skill, orpluginto contribute it to the cc-content plugin."Wait for the answer.
project→ end-user mode;plugin→ plugin-dev mode.
Store the mode — it controls output paths, shared-file handling, and @-imports in all subsequent steps.
Step 2: Find research files
Check whether the staging folder exists and contains .md files:
ls .claude/skill-drafts/<format-name>/ 2>/dev/null && echo "found" || echo "missing"
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 First seen · 509 lines · 63 tokens per session scan B bf1fe2374886
new-content-skill is a skill published in the GitHub repository clever-cc-plugins/cc-content (1 stars, last pushed 10d ago), licensed MIT. It adds 63 tokens to every session and 5,590 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
auditing-config
Audit and optimize an existing Claude Code configuration against current best practices. Use this skill when a user asks to review, improve, clean up, or optimize their Claude Code setup, CLAUDE.md, settings, hooks, MCP servers, or skills. Also use when the user says things like "check my config", "is my CLAUDE.md too…
bootstrapping-config
Bootstrap a best-practice Claude Code configuration for a new or unconfigured project. Use this skill when a user asks to set up Claude Code, initialize a project, create a CLAUDE.md, or configure permissions/hooks/settings for the first time. Also use when the user says things like "set up this project", "configure…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.