agentmods.dev

text.merge_content_into

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

A content-editing routine that places supplied material into a suitable book, slide deck, paper, or blog file. It can inspect the surrounding structure before choosing where the material belongs.

In plain words
What is it for?
Use it to merge content into a named target or find and rank likely targets when no file is specified.
Why use it?
It reduces the risk of putting useful content in the wrong section or disrupting the structure of a larger document.

Skill for Claude Code

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

not rated 158repo +1 today A scan 17 tokens original Apache-2.0

Good fit Use it to merge content into a named target or find and rank likely targets when no file is specified.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/text.merge_content_into
View source ↗ gpsaggese/helpers
Install

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.

Any agent
npx skills add gpsaggese/helpers --skill text.merge_content_into
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/text.merge_content_into/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/text.merge_content_into)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/text.merge_content_into"><img src="https://agentmods.dev/badge/skills/gpsaggese/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/gpsaggese/helpers/text.merge_content_into"><img src="https://agentmods.dev/badge/skills/gpsaggese/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 546 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.00546
Opus 5.5 $0.00007 $0.00218
Sonnet 5.5 $0.00003 $0.00109
Haiku 4.5 $0.00002 $0.00055

Measured yesterday against content hash 7ef3e04b6397, 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 yesterday.

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 · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 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 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 part of a file (e.g., "chapter 3", "slide 12"), open that file and jump to that part
      • If it is a whole file in a book or course (e.g., book_springer/map.md), read map.md to understand the structure of the material
    • 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 dir), using each file's book_map.md or table of contents when one exists
      • Compare the topic of <CONTENT> against each candidate's title, headers, and structure. Rank candidates by relevance
      • If exactly one candidate is a clear match, use it as <TARGET> and tell the user which file was picked and why
      • If several candidates are close, or none is a plausible match, STOP and ask the user to confirm or pick the target. Do not guess
  • Find which part of <TARGET> the content is relevant for
    • If more than one location is plausible, or none fits well, STOP and ask the user where to add the content. Do not guess
  • Propose how to integrate <CONTENT> in <TARGET> using bullet points, following .claude/skills/markdown.rules.md and .claude/skills/text.rules.md

Verification

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

Read the full file on GitHub · 48 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. yesterday First seen · 48 lines · 17 tokens per session scan A 7ef3e04b6397

Subscribe to this mod's changes

text.merge_content_into is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 546 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-11-06.

DocumentsWriting and docs
Related

text.merge_content_into compared with skills from other repositories

text.merge_content_into next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
text.merge_content_intogpsaggese/helpersSkill158todayApache-2.0A17Claude Code
orbit-notionnexu-io/open-designSkill106ktodayApache-2.0A117Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-pluginsSkill35ktodayApache-2.0A123Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skillsSkill49kyesterdayMITA48Claude Code
legal-holdanthropics/claude-for-legalSkill9.9ktodayApache-2.0A68Claude Code
report-to-pdfasgeirtj/system_prompts_leaksSkill71ktodayCC0-1.0A17Claude Code, Codex
artifact-template-minimal-letterheadasgeirtj/system_prompts_leaksSkill71ktodayCC0-1.0A54Claude Code, Codex