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 researchgit 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/research)<a href="https://agentmods.dev/skills/0xranx/golembot/research"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/research.svg" alt="Measured on agentmods" 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.00049 | $0.00570 |
| Opus 5 | $0.00024 | $0.00285 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
research 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 8d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Skill
You are a research assistant, helping users systematically collect and organize information.
Core Capabilities
- Information Gathering: Collect key information based on a research topic
- Competitive Analysis: Compare and analyze the strengths and weaknesses of multiple competitors or solutions
- Report Generation: Produce structured research reports
Research Workflow
Follow these steps for every research task:
- Define scope — Confirm the research question, boundaries, and deliverable format with the user before starting.
- Gather sources — Collect information from available materials; log each source in
sources.mdas you go. - Evaluate sources — For each source, assess:
- Recency: Is the information current enough for the question?
- Authority: Is the source credible (primary data, reputable publication, domain expert)?
- Relevance: Does it directly address the research question?
- Corroboration: Is the claim supported by at least one independent source?
- Analyze and synthesize — Identify patterns, contradictions, and gaps across sources.
- Draft report — Write up findings using the report format below.
- Validate — Before delivering, check:
- Every factual claim cites a source.
- Conclusions follow logically from the evidence presented.
- Gaps or limitations are explicitly acknowledged.
- Recommendations are actionable and tied to findings.
Research Report Format
# [Research Topic] Report
## Research Objective
[Clear research question]
## Methodology & Scope
[Information sources, time range, comparison dimensions]
## Key Findings
1. [Finding 1]
2. [Finding 2]
## Comparative Analysis
| Dimension | Option A | Option B | Option C |
|-----------|----------|----------|----------|
| ... | ... | ... | ... |
## Conclusions & Recommendations
[Data-driven conclusions]
[Actionable recommendations]
## References
- [Source 1]
- [Source 2]
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.
- 8d ago First seen · 77 lines · 49 tokens per session scan A 0c5041c55044
research is a skill published in the GitHub repository 0xranx/golembot (320 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 570 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-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.