Borrowing it
Nothing to install: this file belongs to dogganidhal/noddde. 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/dogganidhal/noddde/main/.claude/skills/update-docs/SKILL.mdgit clone --depth 1 https://github.com/dogganidhal/nodddeWrote 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/dogganidhal/noddde/update-docs)<a href="https://agentmods.dev/skills/dogganidhal/noddde/update-docs"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/update-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/dogganidhal/noddde/update-docs"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00040 | $0.02904 |
| Opus 5.5 | $0.00016 | $0.01162 |
| Sonnet 5.5 | $0.00008 | $0.00581 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade A, and why
update-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 2mo 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 6: Update Documentation
Update documentation pages to reflect the spec changes. Docs must stay in sync with the implementation.
Pipeline step 6 of 6. Called by the /spec orchestrator after step 5 (validation).
Why this step exists: Code and tests can be perfect while documentation silently drifts — stale code examples, undocumented exports, behavioral changes not reflected in guides. This step catches that.
Step 1: Find Spec and Identify Changed Exports
Accept either a spec path or source file path:
- Spec → source: read
source_filefrom frontmatter - Source → spec: replace
packages/core/src/withspecs/core/,.tswith.spec.md
Read the spec completely. Extract:
- The
exportslist from frontmatter - The
docslist from frontmatter (if present) - All behavioral requirements (numbered items in
## Behavioral Requirements) - Any
## Migrationor## Deprecationssections
Determine what changed by comparing against the previous state:
- New spec: Everything is new — all exports need documentation
- Edited spec: Identify which exports were added, removed, or had their signatures changed; which behavioral requirements were added or modified
Step 2: Identify Affected Documentation Pages
Use three strategies in order of priority:
Strategy 1: Frontmatter docs field (primary)
Read the spec's docs frontmatter field. These are explicitly mapped documentation pages.
docs:
- aggregates/overview.mdx
- aggregates/defining-aggregates.mdx
These paths are relative to docs/content/docs/.
Strategy 2: Grep for export references (secondary)
Search for references to the spec's exported symbols in documentation:
grep -rl "ExportName1\|ExportName2" docs/content/docs/ --include="*.mdx"
This catches pages not listed in the docs frontmatter — for example, a concepts/ or design-decisions/ page that references defineAggregate.
Add any discovered pages NOT already in the docs list to the working set, but mark them as "discovered" (handle with more caution — they may only mention the export in passing).
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.
- 2mo ago First seen · 321 lines · 40 tokens per session scan A a578c23d67ea
update-docs is a skill published in the GitHub repository dogganidhal/noddde (52 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 2,904 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-08-30.
Other skills, from other repositories
cratis-chronicle-client-typescript
Use when connecting a standalone Node.js process to Chronicle or diagnosing its decorators, discovery or client lifecycle. Not for React generated proxies or another language's client.
cratis-arc-command-typescript
Use when bootstrapping an Arc Node.js server or defining its TypeScript commands. Not for frontend proxy consumption, validation-only changes or server queries; use the corresponding Arc sibling.
cratis-arc-query-typescript
Use when declaring Arc Node.js read-model queries or observable endpoints. Not for React proxy consumption, server commands or Chronicle event materialization.
cratis-arc-validation-typescript
Use when adding rejection rules, state checks or validation assertions to an Arc Node.js server. Not for defining commands or queries, C# and JVM validators, or append-time uniqueness.
cqrs-event-sourcing-architect
CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).
enterprise-architecture-patterns
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability.