agentmods.dev

docs.add_content

docs.add_content is a skill for Claude Code from gpsaggese/helpers. It costs 11 tokens per session (1,997 once invoked), scanned A, original, Apache-2.0.

A documentation tool that adds supplied content to the appropriate files without repeating information already there.

In plain words
What is it for?
Use it to update Markdown documentation while matching the existing files' structure and writing style.
Why use it?
It reduces duplicate or misplaced text in a documentation set and reports content that was redundant, unsuitable, or conflicting.

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 11 tokens original Apache-2.0

Good fit Use it to update Markdown documentation while matching the existing files' structure and writing style.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/docs.add_content
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 docs.add_content
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 docs.add_content

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/docs.add_content"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/docs.add_content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,997 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.00011 $0.01997
Opus 5.5 $0.00004 $0.00799
Sonnet 5.5 $0.00002 $0.00399
Haiku 4.5 $0.00001 $0.00200

Measured yesterday against content hash 1782532ef5e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs.add_content 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/docs.add_content/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 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 add: text, or a path to a file holding the text
    2. Optionally, the target <TARGET>: a file in <DOCS_DIR> (existing or new) or a header inside it
  • Add the new information in <CONTENT> to the right files in <DOCS_DIR>
  • Never duplicate what the docs already say
  • Report every chunk that was redundant, did not fit, or conflicts with the docs

Conventions

  • Follow the rules in
    • .claude/skills/markdown.rules.md
    • .claude/skills/text.rules.md
    • <DOCS_DIR>/documentation_meta/all.writing_docs.how_to_guide.md, in particular ### Convention for file names, ### Format of each doc, and ### Do not add redundancy
    • <DOCS_DIR>/documentation_meta/all.diataxis.explanation.md to pick the doc type (.tutorial.md, .how_to_guide.md, .reference.md, .explanation.md)
  • Match the style, tone, and header structure of the file being edited

Workflow

Resolve the docs dir

  • Go to the root of the Git work tree 
    > cd $(git rev-parse --show-toplevel)
  • Set <DOCS_DIR>
    • If helpers_root is a submodule of this repo, use helpers_root/docs
      • Check with 
        > git config --file .gitmodules --get-regexp 'submodule\..*\.path' | grep -w helpers_root
    • Otherwise use docs (when the repo is helpers itself)
  • Check that <DOCS_DIR> exists, otherwise STOP and tell the user

Read the content

  • If <CONTENT> is a path, read the file. Never modify or delete it
  • Split <CONTENT> into chunks, each stating one idea, fact, rule, or procedure
    • Keep each example with the chunk it illustrates
    • Drop filler and meta comments (e.g., "add this to the docs")

Survey the docs

  • Read <DOCS_DIR>/README.md for the directory structure and file naming
  • List the doc files 
    > find <DOCS_DIR> -name "*.md" | sort
  • For each chunk, search its key terms, synonyms, tool names, and commands 
    > rg -i "<TERM>" <DOCS_DIR> --glob "*.md"
  • Read in full every matching file, and every file whose name or headers match the topic
    • Do not decide on redundancy from the file name or a grep hit alone

Read the full file on GitHub · 188 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 · 188 lines · 11 tokens per session scan A 1782532ef5e6

Subscribe to this mod's changes

docs.add_content is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 1,997 once invoked, about $0.0000 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.

Writing and docs
Related

docs.add_content compared with skills from other repositories

docs.add_content next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
docs.add_contentgpsaggese/helpersSkill158todayApache-2.0A11Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex