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 Demerzels-lab/elsamultiskillagent --skill reigit clone --depth 1 https://github.com/Demerzels-lab/elsamultiskillagentWrote 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/demerzels-lab/elsamultiskillagent/rei)<a href="https://agentmods.dev/skills/demerzels-lab/elsamultiskillagent/rei"><img src="https://agentmods.dev/badge/skills/demerzels-lab/elsamultiskillagent/rei/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/demerzels-lab/elsamultiskillagent/rei"><img src="https://agentmods.dev/badge/skills/demerzels-lab/elsamultiskillagent/rei.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.00041 | $0.00539 |
| Opus 5 | $0.00020 | $0.00269 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
rei 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 11d 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
Rei Qwen3 Coder
Rei provides Qwen3 Coder via an OpenAI-compatible endpoint at coder.reilabs.org.
Setup via Script
./skills/rei/scripts/setup.sh YOUR_REI_API_KEY
This adds the provider, adds it to the model allowlist, and restarts the gateway.
Setup via Agent
Ask your agent:
"Set up Rei with API key: YOUR_KEY"
The agent will read this skill and run the setup script for you.
Switching Models
Via chat:
/model rei
/model opus
Via script:
./skills/rei/scripts/switch.sh rei
./skills/rei/scripts/switch.sh opus
Via agent:
"Switch to Rei" or "Switch back to Opus"
Revert
If something breaks, restore the backup:
./skills/rei/scripts/revert.sh
Manual Setup
Add to ~/.clawdbot/clawdbot.json:
{
"models": {
"providers": {
"rei": {
"baseUrl": "https://coder.reilabs.org/v1",
"apiKey": "YOUR_API_KEY",
"api": "openai-completions",
"headers": { "User-Agent": "Clawdbot/1.0" },
"models": [{
"id": "rei-qwen3-coder",
"name": "Rei Qwen3 Coder",
"contextWindow": 200000,
"maxTokens": 8192
}]
}
}
},
"agents": {
"defaults": {
"models": {
"rei/rei-qwen3-coder": { "alias": "rei" }
}
}
}
}
Then restart: clawdbot gateway restart
Troubleshooting
403 errors: The User-Agent: Clawdbot/1.0 header is required. The setup script adds this automatically. If you configured manually, make sure the header is present.
"Model not allowed": Rei must be in agents.defaults.models to switch to it. The setup script handles this. For manual setup, add the allowlist entry shown above.
What ships with it
4 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.
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.
- 11d ago First seen · 90 lines · 41 tokens per session scan A cd7788812479
rei is a skill published in the GitHub repository Demerzels-lab/elsamultiskillagent (10 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 539 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…