Borrowing it
Nothing to install: this file belongs to waynesutton/markdown-site. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/waynesutton/markdown-site/main/.cursor/skills/update-project-docs/SKILL.mdgit clone --depth 1 https://github.com/waynesutton/markdown-siteWrote 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/waynesutton/markdown-site/update-project-docs)<a href="https://agentmods.dev/skills/waynesutton/markdown-site/update-project-docs"><img src="https://agentmods.dev/badge/skills/waynesutton/markdown-site/update-project-docs/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/waynesutton/markdown-site/update-project-docs"><img src="https://agentmods.dev/badge/skills/waynesutton/markdown-site/update-project-docs.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.00000 | $0.00513 |
| Opus 5.5 | $0.00000 | $0.00205 |
| Sonnet 5.5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
update-project-docs 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.
What it actually says
Update project docs
Use this skill after completing any feature, fix, or migration to keep the three core project tracking files in sync.
Activate with: @update
Step 1: Get real dates
Run this first:
git log --date=short -n 10
Use actual commit dates. Never use placeholder dates or future months.
Step 2: Update TASK.md
Move completed items into ## Completed with the date:
- [x] Feature name (YYYY-MM-DD)
- [x] Sub-task detail
- [x] Sub-task detail
Add a session update note at the top of ## Current Status:
Session updates complete on YYYY-MM-DD.
If new work is queued, add it under ## To Do.
Step 3: Update changelog.md
Follow https://keepachangelog.com/en/1.0.0/ format. Add the new entry at the top under ## [Unreleased] or as a versioned release:
## [vX.Y.Z] - YYYY-MM-DD
### Added
- Feature name with key details
### Fixed
- Bug description and resolution
### Changed
- What changed and why
Version increment guide (check existing version in changelog.md first):
- New feature: bump minor (2.20.x -> 2.21.0)
- Bug fix or small improvement: bump patch (2.20.0 -> 2.20.1)
Step 4: Update files.md
Only update if new files were added or if existing file descriptions are outdated.
- Add new files to the correct table section
- Keep descriptions to 1-2 sentences, no emoji
- Focus on what the file does and any key implementation details
Checklist
Before calling this done, confirm:
-
git log --date=shortrun to get real dates -
TASK.mdcompleted section updated with date and sub-items -
changelog.mdnew entry added with real version and date -
files.mdupdated if new files exist
Notes
- This skill applies to this project. If the project you are working on does not have these exact files, adapt the steps to whatever tracking files exist.
- Do not create
README.md,CONTRIBUTING.md, or other documentation files unless explicitly requested.
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.
- 1mo ago First seen · 77 lines · 0 tokens per session scan A e27f909700ce
update-project-docs is a skill published in the GitHub repository waynesutton/markdown-site (627 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 513 tokens. 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-08-30.
Other skills, from other repositories
Meeting Action Extractor
Extract decisions, action items, owners, deadlines, and follow-ups from meeting transcripts — structured output for project tracking.
Airtable Manager
Create, read, update, and delete records in Airtable bases — manage data, CRM, and project tracking via Composio.
CRM Management
Maintain and update CRM records.
Culture
Build and maintain team culture.
Onboarding
Design and run onboarding programs.
Scheduling
Schedule and manage social posts.