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 tomzx/agents --skill propagate-changesgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/propagate-changes)<a href="https://agentmods.dev/skills/tomzx/agents/propagate-changes"><img src="https://agentmods.dev/badge/skills/tomzx/agents/propagate-changes/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/tomzx/agents/propagate-changes"><img src="https://agentmods.dev/badge/skills/tomzx/agents/propagate-changes.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.00105 | $0.05211 |
| Opus 5.5 | $0.00042 | $0.02084 |
| Sonnet 5.5 | $0.00021 | $0.01042 |
| Haiku 4.5 | $0.00011 | $0.00521 |
Grade A, and why
propagate-changes 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 22d 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 — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propagate Changes
A change made in one artifact invalidates two things at once: the artifacts built from it, and the artifacts it was built from.
The forward /sdlc pipeline propagates intent downstream, and each review-* skill checks one adjacent pair in isolation.
This skill runs one propagation pass in both directions along the artifact graph.
Downward, it updates dependents: every artifact that still describes the old version is rewritten when the resolution follows from the change.
Upward, it questions premises: every artifact the change depends on is re-checked, and drift is flagged for a human decision instead of being resolved by guesswork.
Wherever two connected artifacts disagree in a way that admits more than one resolution, the pass raises a question rather than picking a side.
Prerequisites
- Working directory is the root of the repository
- A populated
.sdlc/directory (run/sync-sdlcfirst if absent) - At least one feature under
.sdlc/features/N-<slug>/with artifacts present - Read access to the codebase
- Read any files present under
.sdlc/context/for project-level context, and apply their style rules to rewritten artifacts and the report
The Propagation Map
The artifacts of a feature form a directed graph: an artifact is built from the artifacts its edges come from. The canonical map for SDLC features is:
issue
└─> needs-assessment
└─> requirements
└─> specification
├─> lifecycle.md / telemetry.md / observability.md
├─> plan
│ └─> tasks
└─> tests
tasks -> code (implementation)
code -> documentation
code + tests -> PR title and description
Every edge is bidirectional for propagation purposes: downward updates the dependent, upward questions the premise.
If an artifact declares extra dependencies in a depends_on list in its frontmatter, treat those as additional edges.
Direction Semantics
| Direction | What staleness means | Authority | Action |
|---|---|---|---|
| Downward (dependents) | A dependent still describes the old version of the change | The changed artifact is authoritative | Rewrite the dependent when a single resolution follows from the change. Raise a question when more than one resolution exists. |
| Upward (premises) | A premise may be stale, or the change itself may be wrong | Ambiguous by definition | Never rewrite. Classify the drift, and with --fix regress the stale artifact's review verdict so the forward pipeline resyncs it. Raise a question for the human. |
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.
- 22d ago Changed · +24 lines 0fb3eac612d2
- 25d ago Changed ef5db72d77af
- 1mo ago First seen · 410 lines · 105 tokens per session scan A ee51008bc058
propagate-changes is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 5,211 once invoked, about $0.0004 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-09-22.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.