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 flonat/flonat-research --skill update-project-docgit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/update-project-doc)<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.
<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>- NVIDIA SkillSpector pass
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.00050 | $0.02420 |
| Opus 5 | $0.00025 | $0.01210 |
| Sonnet 5 | $0.00010 | $0.00484 |
| Haiku 4.5 | $0.00005 | $0.00242 |
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.
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-closewhen 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:
- Check for
CLAUDE.mdin project root - Check for
README.mdin project root - Scan
docs/anddocs/*/for.mdfiles containing file trees or counts - 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:
- File tree — use
ls -RorGlobto build the actual directory structure (respect.gitignorepatterns, skipout/,__pycache__/,.venv/,node_modules/) - Recent git history —
git log --oneline -20for recent commits - Session logs — read the latest 1-2 files in
log/(if the directory exists) - Bibliography count — count entries in any
.bibfile(s):grep -c '@' *.bib - Symlink targets —
readlinkon any documented symlinks - Context files — read
.context/current-focus.mdor.context/project-recap.mdif present
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.
- 8d ago First seen · 195 lines · 50 tokens per session scan A 434efbf82e65
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.
Other skills, from other repositories
buffer-sizing
Calculate project, feeding, and resource buffers — shared with implementation-planning.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
speckit-companion-specify
../../../.specify/extensions/companion/.specify-dev/agent-commands/claude/speckit-companion-specify/SKILL.md.