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 clix-so/skills --skill user-managementgit clone --depth 1 https://github.com/clix-so/skillsWrote 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/clix-so/skills/user-management)<a href="https://agentmods.dev/skills/clix-so/skills/user-management"><img src="https://agentmods.dev/badge/skills/clix-so/skills/user-management.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.00082 | $0.01067 |
| Opus 5 | $0.00041 | $0.00534 |
| Sonnet 5 | $0.00016 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
clix-user-management 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 7d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- LICENSE.txt 11 KB
- references/debugging.md 840 B
- references/implementation-patterns.md 984 B
- references/logout-and-switching.md 768 B
- references/personalization-and-audience.md 821 B
- references/property-schema.md 1.4 KB
- references/user-management-contract.md 1.4 KB
- scripts/validate-user-plan.sh 2.6 KB runs code
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.
- 7d ago First seen · 117 lines · 82 tokens per session scan A e1e1431ee9c2
clix-user-management is a skill published in the GitHub repository clix-so/skills (5 stars, last pushed 5mo ago), with no licence file. It adds 82 tokens to every session and 1,067 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-31.
Other skills, from other repositories
new
Create a new project to start development quickly.
channel-manager
Configure IM platform channels (Feishu, WeCom, Weixin, Discord, Telegram, DingTalk) for openclacky. Uses browser automation for navigation; guides the user to paste credentials and perform UI steps. Trigger on: "channel setup", "setup feishu", "setup wecom", "setup weixin", "setup wechat", "setup discord", "setup…
yida-data-management
A tool for querying, adding, and updating Yida form records, child tables, process records, and task-center data. It keeps ordinary forms and approval workflows on their separate data interfaces.
yida-get-schema
A command for reading the field IDs, subtable paths, and behavior settings of a Yida form. Yida is a platform for building online forms and business workflows.
yida-canvas-data-binding
A method for connecting a YidaCodeCanvas page to real data from Yida forms, connectors, or same-site APIs. YidaCodeCanvas is the component used to run custom React pages inside Yida.
yida-connector-safe-actions
A method for turning existing API definitions into callable actions in an existing Yida HTTP connector. It reads frontend API wrappers and backend controller definitions to determine the request details.