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 ashishpatill/tell-proof --skill pointer-field-craftgit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/pointer-field-craft)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/pointer-field-craft"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/pointer-field-craft.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.00052 | $0.00393 |
| Opus 5 | $0.00026 | $0.00197 |
| Sonnet 5 | $0.00010 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
pointer-field-craft 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 4d 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.
What it actually says
pointer-field-craft
Build the emitter when trail density must follow hand speed.
Emit by distance, not time (the core mechanism)
E.acc += moved;
let guard = 0;
while (E.acc >= STEP && guard++ < 14) {
E.acc -= STEP;
spawn(/* … */);
}
Timer emission makes spacing ∝ speed — flicks scatter; resting hands pile motes. Cap the loop so teleports / tab restores cannot spawn thousands in one frame.
Place each mote where it is owed
Lay along the segment (t = guard * STEP / moved), not all at the current tip.
Ring-buffer: take the slot before advancing
const i = E.i; E.i = (i + 1) % N; // correct — advance after write
Advancing first makes every mote appear one step behind.
Lag the emitter behind the pointer
Damp toward the pointer so flicks keep slack instead of welding the trail to the cursor.
Also learn
- Idle breath when distance emission would go silent
- Coast instead of hard stop
- Touch +
prefers-reduced-motion→ disable or static - Pause when
document.hiddenor section not intersecting - Prefer canvas overlay; moving emitter solely to raise z-index rarely pays off
Tell constraints
- Default product UI: off (distracts from proof stages)
- Allowed as opt-in on art-directed studio heroes with reduced-motion off and content contrast intact
- Never attach listeners per mote; one pointer listener on the field root
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.
- 4d ago First seen · 52 lines · 52 tokens per session scan A 705dfd467b4b
pointer-field-craft is a skill published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 12d ago), licensed MIT. It adds 52 tokens to every session and 393 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-09-03.
Other skills, from other repositories
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
better-design
Build, improve, and review production interfaces with the Better Design MCP. Use for frontend design, UI, UX, interactions, flows, forms, navigation, components, styling, design systems, accessibility, responsive layouts, motion, React Native, Expo, Shopify, Three.js, and product video work, especially when creating…
Add Claude design-system and accessibility workflows with UX/UI Agent Skills
Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.
ui-designer
Designs and builds interface work on top of the design system the repo already has: layout, spacing, hierarchy, interaction states, and accessible defaults, with creativity calibrated to the surface instead of an unrequested redesign. Use when asked for a new screen, a redesign, empty, loading, and error states, or to…
tw-component
Generate a UI component using correct Tailwind CSS v4 utility classes, CSS variable theming, and accessibility best practices. Prevents v3 syntax hallucination by grounding output in verified v4 patterns.
frontend-design
Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...