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 cenconq25/claude-code-app-studio --skill propagate-design-changegit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/propagate-design-change)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/propagate-design-change"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/propagate-design-change/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/cenconq25/claude-code-app-studio/propagate-design-change"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/propagate-design-change.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.00064 | $0.01846 |
| Opus 5 | $0.00032 | $0.00923 |
| Sonnet 5 | $0.00013 | $0.00369 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
propagate-design-change 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 5d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propagate a Design Change
A PRD edit invalidates downstream work in proportion to how many artifacts referenced it. This skill enumerates that impact in one pass so nothing slips through.
Read-only — no file edits. The user runs follow-up skills (/architecture-decision, /design-system retrofit, /sprint-plan) to apply changes.
Purpose / When to Run
Run when:
- A PRD has just been edited (any section)
- A configurable value, formula, or interface in a PRD has changed
- A new edge case or acceptance criterion was added
- The user wants to know "if I change X, what breaks?"
Inputs
- Path to the changed PRD (required)
- Optional: a description of what changed (free text); skill is more accurate with this hint
- All ADRs in
docs/architecture/ docs/architecture/tr-registry.yamlif present- All stories in
production/epics/ - All other PRDs
Outputs
- A printed change-impact report
Phase 1: Identify the Change
If the user did not describe what changed, ask:
- Prompt: "What changed in this PRD?"
- Options:
New requirement addedExisting requirement modifiedConfigurable value changed (default or range)Edge case added or modifiedAcceptance criterion changedInterface to another system changed (data shape / event)Dependency added / removedI don't know — scan and find out
If user picks "I don't know" or "interface changed", skip to Phase 2 and rely on full scan.
Phase 2: Identify Anchors
Build the list of "anchors" in the changed PRD that downstream work might reference:
- Every TR-ID in the PRD (
TR-<system>-NNN) - Every configurable value name (Section 6)
- Every interface / event / endpoint name (Section 3 / 5)
- The PRD's filename itself (some artifacts cite the path)
- Each entity name from the registry that this PRD owns (
source: <this-prd>)
These anchors are the things downstream artifacts could cite.
Phase 3: Scan for Downstream References
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.
- 5d ago First seen · 217 lines · 64 tokens per session scan A 0a2c215ecb17
propagate-design-change is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,846 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
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…