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 aiko-atami/effectorjs-skills --skill effector-storagegit clone --depth 1 https://github.com/aiko-atami/effectorjs-skillsWrote 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/aiko-atami/effectorjs-skills/effector-storage)<a href="https://agentmods.dev/skills/aiko-atami/effectorjs-skills/effector-storage"><img src="https://agentmods.dev/badge/skills/aiko-atami/effectorjs-skills/effector-storage/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/aiko-atami/effectorjs-skills/effector-storage"><img src="https://agentmods.dev/badge/skills/aiko-atami/effectorjs-skills/effector-storage.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.00081 | $0.00529 |
| Opus 5 | $0.00041 | $0.00264 |
| Sonnet 5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
effector-storage 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 8d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effector Storage Skill
Use this skill to design, implement, and debug effector-storage integrations with predictable runtime behavior.
Workflow
- Classify the request:
adapter-choice: pick the right adapter for environment and data behavior.integration: wirepersist/createPersistinto existing model flow.contracts-errors: validate storage payloads and route failures.sync-debug: investigate cross-tab/query/broadcast synchronization issues.ssr-fallback: make persistence safe across browser/server runtimes.
- Load references progressively:
- Start with
references/core-patterns.md. - Add
references/adapter-matrix.mdwhen adapter selection/configuration is needed. - Add
references/tools-and-composition.mdforasync,either,farcached, or composition recipes. - Add
references/contracts-and-errors.mdfor contracts and error channels. - End with
references/pitfalls-and-checklist.mdbefore finalizing.
- Build answer contract:
- Start with a concrete adapter decision and why.
- Provide a minimal working snippet with explicit key strategy.
- List behavior caveats (init timing, sync limits, validation behavior).
- Add verification steps/tests for the chosen flow.
Defaults
- Target
effector-storagev7.x behavior. - Prefer explicit
keyover implicit store names for portability. - Prefer declarative Effector wiring around
persist(sample/clock/context units). - Keep payloads plain and serialization stable (
deserialize(serialize(x))).
Guardrails
- Do not omit both
keyand store name. - Do not use
source === targetfor non-store units. - Do not assume
pickupstill performs automatic initial restore (it disables it). - Do not assume contract validation prevents writes; invalid values can be persisted and then reported via
fail. - Do not treat
broadcastas durable storage; it is sync-only messaging.
Practical Extras Boundary
For adapters from effector-storage-extras, reuse the same adapter contract and decision flow from this skill, but verify exact API/options in that repository before coding.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 50 lines · 81 tokens per session scan A 2524a4e2bff4
effector-storage is a skill published in the GitHub repository aiko-atami/effectorjs-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 81 tokens to every session and 529 once invoked, about $0.0004 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-31.
Other skills, from other repositories
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
design-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is design-taste-frontend (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
redesign-existing-projects
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
high-end-visual-design
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
industrial-brutalist-ui
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.