update-project-doc

update-project-doc is a skill for Claude Code from flonat/flonat-research. It costs 50 tokens per session (2,420 once invoked), scanned A, original, MIT.

A documentation maintenance workflow for updating an existing project's CLAUDE.md, README.md, or docs with its current facts and structure.

In plain words
What is it for?
Use it to refresh project file trees, timestamps, bibliography counts, task lists, and other structural details in existing documentation.
Why use it?
It keeps documentation from becoming inaccurate after files, milestones, counts, or next steps change.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

Good fit Use it to refresh project file trees, timestamps, bibliography counts, task lists, and other structural details in existing documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flonat/flonat-research/update-project-doc
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 flonat/flonat-research --skill update-project-doc
Clone the repo
git clone --depth 1 https://github.com/flonat/flonat-research

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 update-project-doc

README.md
[![agentmods](https://agentmods.dev/badge/skills/flonat/flonat-research/update-project-doc/github.svg)](https://agentmods.dev/skills/flonat/flonat-research/update-project-doc)
Your own site
<a href="https://agentmods.dev/skills/flonat/flonat-research/update-project-doc"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/update-project-doc/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 update-project-doc

Your own site · 80×15
<a href="https://agentmods.dev/skills/flonat/flonat-research/update-project-doc"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/update-project-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,420 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00050 $0.02420
Opus 5 $0.00025 $0.01210
Sonnet 5 $0.00010 $0.00484
Haiku 4.5 $0.00005 $0.00242

Measured 8d ago against content hash 434efbf82e65, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

update-project-doc 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 8d 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.

skills/update-project-doc/SKILL.md · 195 lines

How it starts

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

Update Project Doc — Refresh Stale Documentation

Scan a project's documentation files and update sections that have drifted from reality: file trees, timestamps, bibliography counts, next steps, skill/hook tallies, and more.

When to Use

  • After significant project work (new files, completed milestones, structural changes)
  • During session-close when offered
  • When the user says "update project docs", "refresh docs", "sync my docs", "update my README"
  • Periodically to keep documentation accurate

What It Does NOT Do

  • Never rewrites research content (hypotheses, arguments, literature, design decisions)
  • Never deletes sections — only updates factual/structural content within existing sections
  • Never creates new documentation files — only updates existing ones

Protocol

Step 1: Detect Documentation Files

Find all documentation files in the project:

  1. Check for CLAUDE.md in project root
  2. Check for README.md in project root
  3. Scan docs/ and docs/*/ for .md files containing file trees or counts
  4. Note which files exist — only update what's present

Special case: Some projects (e.g., the political information paper) have no CLAUDE.md because they use a committed README.md as their primary project documentation instead. This is intentional for repos meant to be shared or published. In these cases, treat README.md as the main documentation file and apply all the same checks to it.

Read each detected file to understand its current content.

Step 2: Gather Current State

Collect the actual state of the project:

  1. File tree — use ls -R or Glob to build the actual directory structure (respect .gitignore patterns, skip out/, __pycache__/, .venv/, node_modules/)
  2. Recent git historygit log --oneline -20 for recent commits
  3. Session logs — read the latest 1-2 files in log/ (if the directory exists)
  4. Bibliography count — count entries in any .bib file(s): grep -c '@' *.bib
  5. Symlink targetsreadlink on any documented symlinks
  6. Context files — read .context/current-focus.md or .context/project-recap.md if present

Read the full file on GitHub · 195 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. 8d ago First seen · 195 lines · 50 tokens per session scan A 434efbf82e65

Subscribe to this mod's changes

update-project-doc is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 16d ago), licensed MIT. It adds 50 tokens to every session and 2,420 once invoked, about $0.0003 per session on Opus 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-03.

Related

Other skills, from other repositories