Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/handarbeit/fabriknpx agentmods add skills/handarbeit/fabrik/experience-baselineWrote 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/handarbeit/fabrik/experience-baseline)<a href="https://agentmods.dev/skills/handarbeit/fabrik/experience-baseline"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/experience-baseline.svg" alt="Measured on agentmods" 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.00132 | $0.05232 |
| Opus 5 | $0.00066 | $0.02616 |
| Sonnet 5 | $0.00026 | $0.01046 |
| Haiku 4.5 | $0.00013 | $0.00523 |
Grade A, and why
experience-baseline 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experience Baseline
Decide once, for the whole product, what someone sees and what they can be asked to do — so that eleven features do not become eleven products.
Read ../../CONVENTIONS.md first. It carries the shared rules — stages, where work
is saved, the tree, markers, interview rules, precedence, gates, decision records and the
baseline status footer. This skill does not repeat them.
This is stage 4 of 5. What you produce is the input the architecture baseline needs.
Why this tier carries the weight
A component defined for one feature is reused by six others; a state defined once applies everywhere; a word chosen here appears on forty screens.
Note the honest limit: the per-feature experience document this is meant to be inherited
by does not exist yet (see the tree in ../../CONVENTIONS.md). Today this baseline is
consumed by stage 5 and by whoever builds. Say that rather than promising an assembly
step nobody has built.
Text is what gets built from
The output of design work is visual. The thing that builds this product reads files.
Text is authoritative for behaviour; the design file is authoritative for appearance.
Where the two meet — a state's signal is appearance that carries behaviour — record the distinguishing dimension and its floor, not the rendering:
"Sync state is distinguished by icon plus word, never colour alone. Legible at arm's length in poor light. Survives a screen reader and translation."
That is implementable, it is a real design decision, and it leaves the rendering to the file. "Saved offline is signalled" is not a decision.
What this is not
Not per-feature flows. Not visual design — no colour values, type scales or spacing systems. If the lead volunteers them as binding, record a pinned reference to the design file rather than transcribing them.
Before starting
Establish the project root as ../../CONVENTIONS.md describes.
If there are no specs, say so and stop. This skill's entire method is derivation from them, and an experience baseline invented from a blank page is the failure this method exists to prevent. If there are specs but no constitution, carry on, say so, and record the absence in the document.
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 · 437 lines · 132 tokens per session scan A 6fc933eba91e
experience-baseline is a skill published in the GitHub repository handarbeit/fabrik (22 stars, last pushed today), licensed Apache-2.0. It adds 132 tokens to every session and 5,232 once invoked, about $0.0007 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
flame-harness-design
Phase 3 — define the Flutter designtokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.
animation-patterns
Framer Motion patterns, page transitions, skeleton loading, scroll-linked animations, and gesture-based interactions for React.
brand-identity
Voice framework, visual identity standards, color palette management, typography specs, brand consistency.
accessibility-patterns
WCAG 2.2 AA compliance, ARIA patterns, keyboard navigation, screen reader optimization.
component-library-patterns
Design system token management, component API design, Storybook, and visual regression testing patterns.
design-loop
Autonomous multi-page site builder using a baton-passing loop. Each iteration reads a task from .design/next-prompt.md, generates a page in HTML/Tailwind, integrates it into the site, verifies visually, then writes the next task to keep the loop alive. Use whenever the user asks to build an entire site autonomously…