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 transactions-locksgit 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/transactions-locks)<a href="https://agentmods.dev/skills/ingvarconsulting/unica/transactions-locks"><img src="https://agentmods.dev/badge/skills/ingvarconsulting/unica/transactions-locks/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/transactions-locks"><img src="https://agentmods.dev/badge/skills/ingvarconsulting/unica/transactions-locks.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.00082 | $0.01795 |
| Opus 5 | $0.00041 | $0.00898 |
| Sonnet 5 | $0.00016 | $0.00359 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
transactions-locks 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.
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.
- 4d ago Changed 1ce8d2979f20
- 5d ago Changed 54f411fad9aa
- 5d ago First seen · 85 lines · 82 tokens per session scan A 97e4cc09d7b4
transactions-locks is a skill published in the GitHub repository IngvarConsulting/unica (191 stars, last pushed today), with no licence file. It adds 82 tokens to every session and 1,795 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-09-03.
Other skills, from other repositories
postmortem
Auto-generates a structured postmortem from a completed campaign. Reads the campaign file, telemetry logs, and feature ledger. Produces a documented analysis of what broke, what the safety systems caught, and what patterns emerged. Can also be invoked manually for any incident.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.
db-repo
A command for working with a 1C configuration repository, which stores versions and controls changes to configuration objects.
db-list
A command for listing and managing the 1C databases registered in a project's .v8-project.json file.
db-load-xml
A command for loading 1C configuration source files from XML into a database. XML files represent the configuration's editable source.
db-cfe-admin
A command for managing configuration extensions attached to a 1C information base, including listing, checking, changing properties, and deleting them.