docs-lifecycle-scan

docs-lifecycle-scan is a skill for Claude Code from amplifthq/opentag. It costs 38 tokens per session (129 once invoked), scanned A, original, MIT.

A documentation maintenance procedure that checks the repository's developing documentation and applies its lifecycle rules.

In plain words
What is it for?
It helps check documentation health when finishing a feature or cleaning up the developing documentation area.
Why use it?
It provides a consistent way to find stale or incorrectly classified documents instead of deciding case by case.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit It helps check documentation health when finishing a feature or cleaning up the developing documentation area.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amplifthq/opentag/docs-lifecycle-scan
About the project

OpenTag connects Slack with coding agents running on a computer controlled by the user, so channel mentions can queue work and return status, decisions, and evidence in the same thread. It is for engineering teams that want to run agents such as Claude Code, Codex, or Cursor against local checkouts through the Agent Client Protocol.

amplifthq/opentag · 0 stars · on GitHub · openmeld.ai

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 amplifthq/opentag --skill docs-lifecycle-scan
Clone the repo
git clone --depth 1 https://github.com/amplifthq/opentag

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-lifecycle-scan

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/amplifthq/opentag/docs-lifecycle-scan"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/docs-lifecycle-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 129 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.00038 $0.00129
Opus 5.5 $0.00015 $0.00052
Sonnet 5.5 $0.00008 $0.00026
Haiku 4.5 $0.00004 $0.00013

Measured 2d ago against content hash 4667c394317c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-lifecycle-scan 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 2d 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.

.claude/skills/docs-lifecycle-scan/SKILL.md · 20 lines

What it actually says

Docs Lifecycle Scan (thin router)

Read developing/README.md before acting. It owns document classification, lifecycle markers, deletion conditions, and remediation. Do not restate those rules here.

Run

pnpm run verify:docs

Use pnpm run verify:docs -- --strict when a blocking result is required. Interpret every result through the owner standard above.

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. 2d ago First seen · 20 lines · 38 tokens per session scan A 4667c394317c

Subscribe to this mod's changes

docs-lifecycle-scan is a skill published in the GitHub repository amplifthq/opentag (0 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 129 once invoked, about $0.0002 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-10-15.