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 clever-cc-plugins/cc-content --skill register-contextgit 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/register-context)<a href="https://agentmods.dev/skills/clever-cc-plugins/cc-content/register-context"><img src="https://agentmods.dev/badge/skills/clever-cc-plugins/cc-content/register-context/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/clever-cc-plugins/cc-content/register-context"><img src="https://agentmods.dev/badge/skills/clever-cc-plugins/cc-content/register-context.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.00079 | $0.01261 |
| Opus 5.5 | $0.00032 | $0.00504 |
| Sonnet 5.5 | $0.00016 | $0.00252 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
register-context 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promote to Context
You are registering an existing file as context in CLAUDE.md so content skills can
discover and load it for future work.
Step 1: Identify the file and target
If $ARGUMENTS contains a file path, use it. Otherwise ask:
"Which file would you like to register as context? (Provide the file path.)"
If $ARGUMENTS also names a target CLAUDE.md explicitly (e.g. "register x in
myproject/press/2026/CLAUDE.md"), record that path. An explicit target is a deliberate
choice — Step 4 uses it directly, no placement questions asked.
Read the file.
Step 2: Suggest a label
Generate a short, descriptive label (2–5 words) based on the file content. Good labels are specific enough to distinguish this file from similar ones in the same project:
- Too generic: "Writing style"
- Good: "Brand voice – recruiting"
- Good: "Whitepaper – AI in HR (Q3 2025)"
- Good: "Audience – enterprise buyers"
Present the suggestion and ask the owner to confirm or change it:
"Suggested label: [label] (or enter your own — no restrictions)"
Step 3: Generate a summary
Write a one-sentence summary (10–25 words) from the file content. The summary is the key signal skills use to decide which file to load for a given task — be specific:
- Too vague: "Writing style guidelines"
- Good: "Formal German, em-dash preferred, no exclamation marks — all corporate copy"
- Good: "Whitepaper on AI in HR published Q3 2025 — use as reference for follow-up content"
- Good: "Three enterprise buyer personas: CHROs, IT directors, and works councils"
Present the suggestion and ask the owner to confirm or change it:
"Suggested summary: [summary] (or enter your own)"
Step 4: Determine the target CLAUDE.md
If an explicit target was named in $ARGUMENTS (Step 1), use it directly and skip to Step 5 —
no placement question, that's the point of naming it explicitly.
Otherwise, scan for candidates:
find . -name "CLAUDE.md" -not -path '*/.git/*' -not -path '*/node_modules/*' | sort
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.
- 1mo ago First seen · 140 lines · 79 tokens per session scan A e701da6fa434
register-context is a skill published in the GitHub repository clever-cc-plugins/cc-content (1 stars, last pushed 14d ago), licensed MIT. It adds 79 tokens to every session and 1,261 once invoked, about $0.0003 per session on Opus 5.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
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
recall
Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
assigns-audit
Inspect LiveView socket assigns for memory bloat — missing temporaryassigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporaryassigns.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
wicked-garden-repo-learn
Learn an unfamiliar repo the way a senior engineer does: follow where the code actually churns, find what that churn touches that the rest of the system leans on, read the load-bearing code for real, then write down BOTH what you learned (knowledge) and what should hold (policies) — as inert estate proposals a human…