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 effectorjsgit 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/effectorjs)<a href="https://agentmods.dev/skills/aiko-atami/effectorjs-skills/effectorjs"><img src="https://agentmods.dev/badge/skills/aiko-atami/effectorjs-skills/effectorjs.svg" alt="Measured on agentmods" 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.00097 | $0.01164 |
| Opus 5 | $0.00048 | $0.00582 |
| Sonnet 5 | $0.00019 | $0.00233 |
| Haiku 4.5 | $0.00010 | $0.00116 |
Grade A, and why
effectorjs 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EffectorJS Skill
Use this skill to produce deterministic, scope-safe Effector solutions for new features, refactors, and code reviews.
Workflow
- Classify the request:
modeling: create or extend stores/events/effects.refactor: replace anti-patterns with declarative flows.ssr: implement or debug scope-safe SSR.review: assess risks, regressions, and missing tests.legacy-migration: move old patterns to modern v23+ safely.
- Load only required references:
- Always start with
references/core-patterns.md. - Always load
references/lint-derived-best-practices.mdafter core patterns to enforce plugin-backed best practices. - Add
references/explicit-start.mdwhen task touches app bootstrap, startup logic, initialization order, tests, scope, or SSR. - Add
references/computation-priority.mdwhen task touches ordering,watch, sequencing, race-like behavior, or side effects placement. - Add
references/react-ssr-scope.mdwhen React/SSR/scope appears. - Add
references/solid-scope.mdwhen Solid integration appears. - Add
references/vue-scope.mdwhen Vue integration appears. - Add
references/anti-patterns-and-fixes.mdwhen fixing or reviewing existing logic. - Add
references/legacy-migration-map.mdwhen deprecated APIs/imports are present. - End with
references/checklists.mdfor acceptance criteria.
- Build solution in this order:
- Model atomic stores and explicit events.
- Define explicit app start (
appStarted) and keep startup wiring declarative. - Move side effects to effects.
- Connect units with
samplefirst; useattachfor effect composition. - Apply scope-first rules (
fork,allSettled) for tests, SPA bootstrap boundaries, and SSR. - For UI frameworks, use
useUnitand correct provider wiring.
- Produce output contract:
- Proposed model topology (stores/events/effects and responsibilities).
- Wiring snippets (
sample,attach,splitif needed). - Scope/SSR notes when applicable.
- Lint-derived conformance notes for naming/dataflow/scope/react constraints.
- Test scenarios and acceptance checklist.
What ships with it
12 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.
- agents/openai.yaml 359 B
- README.md 1.3 KB
- references/anti-patterns-and-fixes.md 1.8 KB
- references/checklists.md 2.9 KB
- references/computation-priority.md 1.2 KB
- references/core-patterns.md 2.4 KB
- references/explicit-start.md 1.7 KB
- references/legacy-migration-map.md 2.0 KB
- references/lint-derived-best-practices.md 3.5 KB
- references/react-ssr-scope.md 2.2 KB
- references/solid-scope.md 1.7 KB
- references/vue-scope.md 1.6 KB
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 · 90 lines · 97 tokens per session scan A 7b26838f4cca
effectorjs is a skill published in the GitHub repository aiko-atami/effectorjs-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 97 tokens to every session and 1,164 once invoked, about $0.0005 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.