Borrowing it
Nothing to install: this file belongs to RorroRojas3/awesome-claude-copilot. 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/RorroRojas3/awesome-claude-copilot/main/.claude/commands/ngrx-signals-sync.mdgit clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilotWrote 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/commands/rorrorojas3/awesome-claude-copilot/ngrx-signals-sync)<a href="https://agentmods.dev/commands/rorrorojas3/awesome-claude-copilot/ngrx-signals-sync"><img src="https://agentmods.dev/badge/commands/rorrorojas3/awesome-claude-copilot/ngrx-signals-sync/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/commands/rorrorojas3/awesome-claude-copilot/ngrx-signals-sync"><img src="https://agentmods.dev/badge/commands/rorrorojas3/awesome-claude-copilot/ngrx-signals-sync.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.00024 | $0.01164 |
| Opus 5 | $0.00012 | $0.00582 |
| Sonnet 5 | $0.00005 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
ngrx-signals-sync scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(node:*), Bash(curl:*), Bash(cp:*), Bash(git status:*), Bash(git diff:*), Read, Edit, Glob, Grep This is a copy
91% identical to ngrx-signals-sync — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh the ngrx-signal-store skill against the official NgRx docs.
The skill is pinned to a snapshot recorded in .claude/skills/ngrx-signal-store/sources.json: a blob sha per upstream doc page, the @ngrx/signals version, and a mapsTo list saying which skill file each page feeds.
1. Check for drift
node .claude/skills/ngrx-signal-store/scripts/check-updates.mjs --json
Branch on the exit code — it is the contract:
0— up to date. Print the one-line summary and stop immediately. Do not read files, do not edit anything, do not touch git. This is the path that runs almost every week and it should cost close to nothing. Resist the urge to "just double-check" the references; the shas already did.1— the check failed (network, rate limit, bad JSON). Report the error and stop. Do not edit anything on the basis of a failed check — a rate-limited run tells you nothing about upstream.10— drift detected. Continue below.
If the user passed --check-only, print the drift report and stop here without editing.
2. Read what actually changed
The report gives you changed (pages whose content moved), added, removed, affectedFiles (the union of the changed pages' mapsTo), rawUrls, and a version delta.
Fetch only the changed pages:
curl -sSL <rawUrl>
Upstream markdown wraps code in ngrx-code-example, ngrx-code-tabs, and ngrx-docs-alert web components. Strip the wrappers, but read the inform and warn alerts carefully — that is where the official best-practice guidance lives, and a change to one of those is usually the most important thing in the diff.
3. Propagate only what matters
Read the affected skill file(s) named in affectedFiles and compare semantically.
Propagate: new, renamed, or removed APIs; a changed default; a changed recommendation; a new idiom in an example; a deprecation; a version bump.
Ignore: prose reflow, typo fixes, link changes, and site-chrome churn. A blob sha moves for all of those. Rewriting a reference file on every sha change is how the skill slowly degrades into a bad paraphrase of the docs — the sha tells you where to look, not what to write.
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.
- 9d ago First seen · 79 lines · 24 tokens per session scan A c7ab57e72e14
ngrx-signals-sync is a command published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 14d ago), licensed MIT. It adds 24 tokens to every session and 1,164 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to ngrx-signals-sync, differing in 16 lines, and is treated as a copy.
Other commands, from other repositories
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
frontend-3d
You are an expert in 3D web development using Three.js, React Three Fiber, WebGL, and WebGPU. You create immersive 3D experiences for the web.
frontend-design
Read and follow the instructions in agents/frontend-design/design-all.md. Also read all referenced files in agents/frontend-design/reference/ as needed for the task.
get-component-source
The full TSX source of a component (append " demo" for its usage example).