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 drivestream-lab/prayog-skills --skill update-documentsgit clone --depth 1 https://github.com/drivestream-lab/prayog-skillsWrote 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/drivestream-lab/prayog-skills/update-documents)<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/update-documents"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/update-documents/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/drivestream-lab/prayog-skills/update-documents"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/update-documents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00094 | $0.04066 |
| Opus 5 | $0.00047 | $0.02033 |
| Sonnet 5 | $0.00019 | $0.00813 |
| Haiku 4.5 | $0.00009 | $0.00407 |
Grade A, and why
update-documents 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 10d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documents — Cross-Document Change Propagation
Purpose
Propagates verified corrections and decisions across a set of related documents. It determines where an approved decision must be reflected; it does not decide what the decision should be.
When to use:
- A fact or assumption was wrong and multiple documents reference it
- New information (design, stakeholder input, discovery) must be reflected across existing docs
- Terminology is changing across a document set
- A feature or scope item is being added, deferred, or removed
- After
review-findings— apply an approvedResolution-*.mdacross PRD + integration stubs
Domain-agnostic. Works on any document type — requirements, PRDs, meeting notes, design specs, technical docs.
Lab handoff: review-findings produces canonical
prd/reports/Resolution-{INIT}.md. Use the Decisions table (CHG-* →
VF-*) plus Approved Fixes, Confirmed Items, Rejected Items, and
Added as Open Questions as the change set (Phase 1). Typical scope:
prd/INIT-*.md, docs/cross-service-lab.md, per-repo 03-integrations.md /
route maps. Prefer assigning/preserving CAP-* / REQ-* / OQ-* when the
resolution asks for product-id updates.
Spec PR (app repo): When drafting docs/specification/product/INIT-*.md, engineering uses /spec-draft on branch chore/INIT-*-spec-{repo}. Wave IDs must match PRD §4.0 / §4.5. Product ids use REQ-* (legacy FR-* ≡ same number). Gate: launchpad playbook/delivery-workflow.md + playbook/spec-layout.md.
Conventions: prayog-skills/references/id-conventions.md,
prayog-skills/references/artifact-write-contract.md.
Operating modes
Select exactly one mode during intake.
Resolution mode (preferred after review-findings)
Use when the input is canonical Resolution-{INIT}.md (or legacy Resolution-*.md).
- The Resolution file is the semantic decision source.
- Apply only rows with a
CHG-*(or legacy approved sections): Approved Fixes, Confirmed Items, Rejected Items, Added as Open Questions, and Modified / custom recommendations. - Exclude Skipped items.
- Preserve
source_finding: VF-*on every change row. - Do not ask the user to re-decide completed resolution rows.
- If a row lacks exact action text, ownership, or other information required to
apply it, classify it
NEEDS DECISIONand return it toreview-findings. - Present the resolved change-set summary for visibility, then use the detailed change manifest as the single approval gate before editing.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 343 lines · 94 tokens per session scan A f7701cf29002
update-documents is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 94 tokens to every session and 4,066 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…