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 lessthanno/Layntra --skill poster-examplegit clone --depth 1 https://github.com/lessthanno/LayntraWrote 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/lessthanno/layntra/poster-example)<a href="https://agentmods.dev/skills/lessthanno/layntra/poster-example"><img src="https://agentmods.dev/badge/skills/lessthanno/layntra/poster-example/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/lessthanno/layntra/poster-example"><img src="https://agentmods.dev/badge/skills/lessthanno/layntra/poster-example.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.00039 | $0.00263 |
| Opus 5.5 | $0.00016 | $0.00105 |
| Sonnet 5.5 | $0.00008 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
poster-example 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 2mo 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
Layntra poster example
This is an optional example built on the core $layntra control policy. It must
not activate for general product design, Figma editing, or an unrelated request.
Follow the core Layntra workflow without exception:
- Check
get_statusand inspect the explicit target. - Present a bounded plan and say that Figma has not changed.
- Wait for
$layntra applyin the same Codex task. - Pass the captured
expectedContextto generic writes. - Re-inspect and report observed results plus
Command + Zrecovery.
Available poster tools include list_templates, replace_guest_photo,
set_event_details, create_waic_template, create_crossborder_template,
place_guest_asset, and the redesign_crossborder_* tools. Use them only when
the explicit request matches. Confirm local image paths exist before image work.
Never let this example redefine connection, targeting, confirmation, deletion, or verification rules from the core Layntra Skill.
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.
- 2mo ago First seen · 26 lines · 39 tokens per session scan A b367c7f1b0eb
poster-example is a skill published in the GitHub repository lessthanno/Layntra (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 263 once invoked, about $0.0002 per session on Opus 5.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
frontend-design
Use when building UI components, making design decisions for frontend work, reviewing UI implementation quality, or planning interaction patterns.
design-system-quality
Use when reviewing UI/frontend code, conducting PR reviews for components, checking design system compliance, or after any UI component work.
brand-guidelines
Use when user mentions "brand", "Open Session colors", "Aperol", "Charcoal", "Vanilla", "brand guidelines", or works on UI following Open Session standards.
lay-ui
Designer-paced, three-station workflow for translating Figma designs into production-ready code. Components are built one at a time with conversational review between each. Use when the user invokes "lay-ui", says "lay out the UI", asks to walk through a Figma file component-by-component, or wants a paced…
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
visualize
Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.