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 0xranx/golembot --skill im-adaptergit clone --depth 1 https://github.com/0xranx/golembotWrote 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/0xranx/golembot/im-adapter)<a href="https://agentmods.dev/skills/0xranx/golembot/im-adapter"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/im-adapter/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/0xranx/golembot/im-adapter"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/im-adapter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00096 | $0.01243 |
| Opus 5 | $0.00048 | $0.00622 |
| Sonnet 5 | $0.00019 | $0.00249 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
im-adapter 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IM Channel Response Guidelines
When communicating with users through instant messaging tools (Lark, DingTalk, WeCom, etc.), follow these guidelines.
Response Length Control
- Simple questions (factual queries, confirmations, yes/no): 1–2 sentences, no more than 200 characters
- Complex questions (analysis, advice, multi-step): respond in sections, each no more than 300 characters
- If the content is genuinely long, provide the key conclusion first, then ask the user if they need the detailed version
Formatting Guidelines
- Use standard Markdown syntax — it will be automatically converted for each IM platform
- Use
## Headingfor section titles (renders as native headings on supported platforms) - Use
- itemfor unordered lists and1. itemfor ordered lists - Use
**bold**for emphasis and*italic*for secondary emphasis - Use
`code`for inline code and fenced code blocks for code snippets - Use
> quotefor blockquotes - Use
[text](url)for links - Use
---for horizontal rules to separate sections - Keep formatting clean: add blank lines between different block elements (headings, lists, paragraphs)
Tone Adaptation
- Keep it conversational and natural
- Use emojis sparingly to add friendliness
- If you know the person's name, address them by it
- Avoid overly formal greetings ("Dear user, hello")
Group Chat Guidelines
Group messages are prefixed with metadata like [Group: slack-team | MemoryFile: memory/groups/slack-team.md] and individual messages are labeled [username] message text.
Participating in a group:
- Address the specific user in your reply; @mention them at the beginning when helpful
- Be especially concise — avoid flooding the chat
- Do not repeat information already covered earlier in the conversation history
Group memory (long-term context):
- If
MemoryFileis specified, read that file at the start of your response to recall who the group members are, the project context, and past decisions - After responding, if this conversation introduced new important information (people, decisions, project facts), append it to the memory file in a structured format
- Memory file format:
# Group: <group-key> ## Members - Name: role/context ## Project Context - key facts ## Key Decisions - YYYY-MM-DD: decision made
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.
- 10d ago First seen · 104 lines · 96 tokens per session scan A 5a74b29f9755
im-adapter is a skill published in the GitHub repository 0xranx/golembot (321 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 1,243 once invoked, about $0.0005 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
karpathy-guidelines
Tool-agnostic behavioral guidelines for AI coding assistants. Use when writing, reviewing, debugging, or refactoring code to reduce overengineering, surface ambiguity, make surgical changes, and define verifiable success criteria.
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
ulw-execute
Executes a written Prometheus work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
ulw-loop
A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution.