helpers: Skill for Claude Code

.claude/skills/text.merge_content_into/SKILL.md

text.merge_content_into is a skill for Claude Code from causify-ai/helpers. It costs 17 tokens per session (588 once invoked), scanned A, original, Apache-2.0.

A writing task that places supplied content into a book, slide deck, paper, or blog while avoiding duplication. It can find a suitable target when one is not specified.

In plain words
What is it for?
Use it to propose where and how an idea, section, or passage should be added to existing written material.
Why use it?
It removes the need to search through related documents and decide manually where new material belongs.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

This is causify-ai/helpers's own configuration. It tells Claude Code how to work on helpers itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything helpers configures →

Reuse

Borrowing it

Nothing to install: this file belongs to causify-ai/helpers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/causify-ai/helpers/master/.claude/skills/text.merge_content_into/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/causify-ai/helpers

Made for: Claude Code.

Wrote 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.

agentmods badge for text.merge_content_into

README.md
[![agentmods](https://agentmods.dev/badge/skills/causify-ai/helpers/text.merge_content_into/github.svg)](https://agentmods.dev/skills/causify-ai/helpers/text.merge_content_into)
Your own site
<a href="https://agentmods.dev/skills/causify-ai/helpers/text.merge_content_into"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/text.merge_content_into/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.

agentmods 80×15 button for text.merge_content_into

Your own site · 80×15
<a href="https://agentmods.dev/skills/causify-ai/helpers/text.merge_content_into"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/text.merge_content_into.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 588 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00588
Opus 5.5 $0.00007 $0.00235
Sonnet 5.5 $0.00003 $0.00118
Haiku 4.5 $0.00002 $0.00059

Measured 1mo ago against content hash 02ffce712772, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

text.merge_content_into 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.

.claude/skills/text.merge_content_into/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

  • The user passes, in this order:
    1. The content <CONTENT> to incorporate
    2. Optionally, the target <TARGET>: a file (e.g., a book, slides, paper, blog) or a reference to a part of a file (e.g., a chapter, section, slide number)
  • Propose where and how to include <CONTENT> in <TARGET>

Workflow

  • Read the proposed content <CONTENT>
  • Resolve <TARGET>
    • If <TARGET> was passed:
      • If it is a reference to a part of a file (e.g., "chapter 3", "slide 12"), open that file and jump to that part
      • If it is a whole file and it belongs to a book / course (e.g., book_springer/map.md), read the map.md to understand the structure of the material covered
    • If <TARGET> was not passed, find it
      • List candidate files for <CONTENT> (e.g., books, slides, papers, blog posts under the relevant course or project directory, using each file's book_map.md or table of contents when one exists)
      • Compare the topic of <CONTENT> against each candidate's content (title, headers, structure) and rank candidates by relevance
      • If exactly one candidate is a clear, unambiguous match, use it as <TARGET> and tell the user which file was picked and why
      • If several candidates are close in relevance, or none is a plausible match, STOP and ask the user to confirm or pick the target instead of guessing
  • Find out which part of <TARGET> the content is relevant for
    • If more than one location is plausible, or no location fits well, STOP and ask the user to clarify where to add the content instead of guessing
  • Propose how to integrate the <CONTENT> in <TARGET> using bullet points following .claude/skills/markdown.rules.md and .claude/skills/text.rules.md

Verification

  • Confirm <TARGET> is either the one the user passed or one the user confirmed, rather than guessed
  • Confirm the proposed location exists in <TARGET> (e.g., a real chapter or slide)
  • Confirm the proposal follows .claude/skills/markdown.rules.md and .claude/skills/text.rules.md
  • Confirm the user was asked for clarification if the file or the location within it was ambiguous, rather than either being guessed

Read the full file on GitHub · 52 lines

Changes

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.

  1. 1mo ago First seen · 52 lines · 17 tokens per session scan A 02ffce712772

Subscribe to this mod's changes

text.merge_content_into is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 588 once invoked, about $0.0001 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-09-16.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens