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 demark-pro/skills --skill effector-fsdgit clone --depth 1 https://github.com/demark-pro/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/demark-pro/skills/effector-fsd)<a href="https://agentmods.dev/skills/demark-pro/skills/effector-fsd"><img src="https://agentmods.dev/badge/skills/demark-pro/skills/effector-fsd.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.00063 | $0.02990 |
| Opus 5 | $0.00032 | $0.01495 |
| Sonnet 5 | $0.00013 | $0.00598 |
| Haiku 4.5 | $0.00006 | $0.00299 |
Grade A, and why
effector-fsd 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 7d 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effector + Feature-Sliced Design Skill
Purpose
Use this skill for project structure in applications that combine Feature-Sliced Design with the Effector ecosystem.
This skill answers:
- where code belongs in
app,pages,widgets,features,entities,shared - how Effector models are split by ownership
- where Farfetched queries/mutations/contracts/barriers live
- how Atomic Router routes and protected routes are placed
- how Next.js
app/pagesframework folders coexist with FSD layers - how public APIs,
@xcross-imports, and import boundaries work - how to review and lint FSD architecture with Steiger
Use effector-ecosystem alongside this skill for exact Effector/Farfetched/React/Next.js API usage. This skill owns placement and structure; effector-ecosystem owns reactive code semantics.
Activation triggers
Use this skill when the user asks about:
- FSD, Feature-Sliced Design, layers, slices, segments, public API
- where to place
model,ui,api,lib,route.ts, contracts, mappers, forms, queries, mutations, barriers, widgets, providers, or adapters - refactoring
src/api,src/components,src/store,src/hooks,src/utilsinto FSD - protected routes/auth flow placement
- Next.js + FSD folder conflicts
- import boundary violations, direct imports, cross-imports,
@x - Steiger or FSD linting
- reviewing an Effector project for architecture boundaries
First response behavior
When the user asks a placement question, answer with:
- The layer/slice/segment where the code belongs.
- The reason in FSD terms: responsibility, dependency direction, ownership.
- The Effector-specific boundary: which model owns the event/store/query/mutation/route.
- A small folder tree or import example.
- Anti-patterns to avoid.
When the question is mostly about exact Effector/Farfetched API syntax, defer to effector-ecosystem but keep placement guidance here.
Full audit mode
When the user asks for a full FSD/Effector architecture audit, do not only check import direction and folder names. Also inspect ownership of cross-cutting Effector flows:
What ships with it
23 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 290 B
- examples/auth-flow-fsd.md 862 B
- examples/generic-list-page-fsd.md 1.9 KB
- examples/nextjs-effector-fsd.md 1.4 KB
- examples/protected-routes-auth-farfetched-fsd.md 6.2 KB
- references/00-source-policy.md 2.3 KB
- references/01-core-rules.md 3.8 KB
- references/02-effector-placement.md 4.6 KB
- references/03-layer-recipes.md 3.7 KB
- references/04-routing-nextjs.md 4.2 KB
- references/05-farfetched-placement.md 6.0 KB
- references/06-public-api-imports.md 4.8 KB
- references/07-review-checklist.md 5.8 KB
- references/08-anti-patterns.md 6.6 KB
- references/09-migration-playbook.md 4.0 KB
- references/10-tooling.md 2.7 KB
- references/11-effector-audit-ownership.md 9.3 KB
- templates/app-structure.md 822 B
- templates/entity-slice.md 905 B
- templates/feature-slice.md 946 B
- templates/page-slice.md 1.3 KB
- templates/steiger.config.ts 538 B runs code
- templates/widget-slice.md 512 B
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.
- 7d ago First seen · 437 lines · 63 tokens per session scan A 43984dbff9a8
effector-fsd is a skill published in the GitHub repository demark-pro/skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 2,990 once invoked, about $0.0003 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
baoyu-markdown-to-html
Converts Markdown to styled HTML with WeChat-compatible themes. Supports code highlighting, math, Mermaid (rendered to PNG via headless Chrome), PlantUML, footnotes, alerts, infographics, and optional bottom citations for external links. Use when user asks for "markdown to html", "convert md to html", "md 转 html"…
extract-design-system
Extract design primitives from a public website and generate starter token files for your project.
cesiumjs-camera
CesiumJS camera control - Camera, flyTo, lookAt, setView, ScreenSpaceCameraController, CameraEventAggregator, flight animation. Use when positioning the camera, creating flyTo animations, constraining user navigation, tracking entities, or converting between screen and world coordinates.
cesiumjs-custom-shader
CustomShader authoring — vertexShaderText and fragmentShaderText against VertexInput, FragmentInput, FeatureIds, Metadata, czmmodelMaterial. Use when reading EXTmeshfeatures or EXTstructuralmetadata property textures/tables, vertex displacement, or shading VoxelPrimitive.
cesiumjs-primitives
CesiumJS primitives and geometry - Primitive, GeometryInstance, Appearance, BufferPrimitive collections, GeoJsonPrimitive, Billboard/Label/PointPrimitive collections, built-in geometry shapes, ground primitives, classification. Use when rendering performance-critical static or vector geometry, loading GeoJSON without…
cesiumjs-time-properties
CesiumJS time, properties, and animation - Clock, JulianDate, TimeInterval, Property, SampledProperty, CallbackProperty, PathMode, interval and sampled path materials, interpolation, splines, CZML temporal data. Use when making entity attributes or path materials time-dynamic, configuring the simulation clock…