Borrowing it
Nothing to install: this file belongs to rodydavis/signals.dart. 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/rodydavis/signals.dart/main/.agents/skills/update-preact/SKILL.mdgit clone --depth 1 https://github.com/rodydavis/signals.dartWrote 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/rodydavis/signals.dart/update-preact)<a href="https://agentmods.dev/skills/rodydavis/signals.dart/update-preact"><img src="https://agentmods.dev/badge/skills/rodydavis/signals.dart/update-preact/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/rodydavis/signals.dart/update-preact"><img src="https://agentmods.dev/badge/skills/rodydavis/signals.dart/update-preact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00990 |
| Opus 5 | $0.00015 | $0.00495 |
| Sonnet 5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
update-preact 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updating Preact JS Submodule and preact_signals Package
This guide details the systematic process for updating the pinned Preact.js Signals JS/TS git submodule (third_party/preactjs_signals) and porting its structural updates, algorithmic changes, and optimizations into the Dart preact_signals package.
1. Upstream Submodule Management
The upstream JavaScript/TypeScript implementation is tracked via a Git submodule located at third_party/preactjs_signals.
A. Initializing and Synchronizing the Submodule
If the submodule is not initialized, run:
git submodule update --init --recursive
B. Pinned Submodule Version Upgrade
To upgrade the pinned submodule version:
- Navigate to the submodule directory:
cd third_party/preactjs_signals - Fetch all latest upstream branches and tags:
git fetch --tags origin - Checkout the desired release tag or commit hash:
git checkout tags/v1.3.0 # or specific tag/commit hash - Return to the root workspace directory and stage the updated submodule pointer:
cd ... git add third_party/preactjs_signals
2. Reviewing Upstream Core Architecture Changes
Once the submodule is checked out to the new version, review the differences inside Preact's TypeScript core codebase:
- Core Primitive File: third_party/preactjs_signals/packages/core/src/index.ts
- Test Suite File: third_party/preactjs_signals/packages/core/test/index.test.ts
Compare changes to locate:
- Algorithmic Optimizations: Refinements in graph tracking, batch processing, or lazy evaluation cycles.
- Bug Fixes: Handling of edge-case memory leaks, exception propagates, or subscription-tracking re-entrancy issues.
- API Contracts: New methods or configuration parameters added to
Signal,Computed, orEffect.
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 · 106 lines · 31 tokens per session scan A 46e5010202a7
update-preact is a skill published in the GitHub repository rodydavis/signals.dart (814 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 990 once invoked, about $0.0002 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-30.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
dart-3-updates
Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.
effective-dart
Use when writing Dart code, reviewing for style, refactoring naming, adding doc comments, structuring imports, or enforcing type annotations.
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
dart-expert
Expert-level Dart, Flutter, mobile development, and cross-platform apps. Use when the user mentions Flutter, mobile, cross platform, or widgets, or when the task involves Dart Language or Flutter Framework.