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 IngvarConsulting/unica --skill form-eventsgit clone --depth 1 https://github.com/IngvarConsulting/unicaWrote 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/ingvarconsulting/unica/form-events)<a href="https://agentmods.dev/skills/ingvarconsulting/unica/form-events"><img src="https://agentmods.dev/badge/skills/ingvarconsulting/unica/form-events/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/ingvarconsulting/unica/form-events"><img src="https://agentmods.dev/badge/skills/ingvarconsulting/unica/form-events.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.00081 | $0.01586 |
| Opus 5 | $0.00041 | $0.00793 |
| Sonnet 5 | $0.00016 | $0.00317 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
form-events 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago Changed c50e70205e67
- 6d ago Changed e637cdc66828
- 6d ago Changed 579a00554c4d
- 10d ago First seen · 77 lines · 81 tokens per session scan A 44eb9f43d303
form-events is a skill published in the GitHub repository IngvarConsulting/unica (192 stars, last pushed today), with no licence file. It adds 81 tokens to every session and 1,586 once invoked, about $0.0004 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
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
form-add
A tool for adding an empty managed form to a 1C object such as a document, catalogue, or information register. A managed form is the screen users use to view or edit that object in 1C.
form-edit
A tool for modifying an existing managed form in 1C by adding screen elements, fields, commands, and event handlers. Event handlers are code routines that run when something happens, such as a field changing.
feature-dev
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
moss-html
Author self-contained moss-html blocks for genuine interactive design artifacts, embedded HTML previews, prototypes, and behavior demonstrations that native Moss nodes cannot represent.
swiftui-app-architecture-workflow
Guide SwiftUI app-structure decisions for Apple apps across App, scenes, commands, focus, environment, preferences, window and document coordination, and reusable view composition. Use when the user wants help deciding where ownership belongs in a SwiftUI app, which data-flow mechanism fits a responsibility, or how to…