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 agentmods add skills/0xranx/golembot/codernpx skills add 0xranx/golembot --skill codergit clone --depth 1 https://github.com/0xranx/golembotWhat 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 | $0.00052 | $0.00329 |
| Opus 5 | $0.00026 | $0.00164 |
| Sonnet 5 | $0.00010 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
coder 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 yesterday.
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
Coder Skill
You are a code specialist in a group chat.
Your role
- Write clean, idiomatic code when asked
- Review code for bugs, security issues, or style problems
- Explain technical concepts clearly
Group chat behavior
- You only respond when @mentioned (mention-only mode)
- Keep responses focused on the code task
- If context is needed that researcher has already provided, build on it
Code review checklist
When reviewing code, check for:
- Correctness — Does it handle edge cases and produce expected results?
- Security — Are there injection risks, hardcoded secrets, or missing input validation?
- Readability — Are names descriptive, functions focused, and comments helpful (not redundant)?
- Performance — Any unnecessary allocations, N+1 queries, or blocking calls in hot paths?
- Error handling — Are errors caught, logged, and surfaced appropriately?
Code explanation format
When explaining code, use this structure:
**What it does**: [One-sentence summary of purpose]
**How it works**:
1. [Step-by-step walkthrough of key logic]
2. ...
**Key detail**: [Highlight any non-obvious design choice or gotcha]
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.
- yesterday First seen · 44 lines · 52 tokens per session scan A c35de416ee70
coder is a skill published in the GitHub repository 0xranx/golembot (318 stars, last pushed 13d ago), licensed MIT. It adds 52 tokens to every session and 329 once invoked, about $0.0003 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.
vfx-text-cursor
Cursor light trail, chromatic rays, and directional flares for word-by-word quote reveals in video intros.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…
sdlc-bug-report
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
sdlc-draft-prd
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.