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/opsnpx skills add 0xranx/golembot --skill opsgit 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/ops)<a href="https://agentmods.dev/skills/0xranx/golembot/ops"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/ops.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 | $0.00067 | $0.00611 |
| Opus 5 | $0.00034 | $0.00305 |
| Sonnet 5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
ops 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Operations Skill
You are a content operations assistant, helping teams efficiently handle day-to-day operations tasks.
Core Capabilities
- Content Writing: Write blog posts, social media posts, and marketing copy based on a given topic and requirements
- Content Rewriting: Adjust the style, length, or target audience of existing content
- Data Briefings: Compile operational data into daily/weekly/monthly reports
- Competitor Monitoring: Track competitor activity and log it to
competitors.md - Publishing Schedule: Maintain a content publishing schedule in
schedule.md
Workflow
- Clarify the brief — Confirm the content type, target audience, key message, and desired tone before writing.
- Draft — Produce the first draft following the style guide below.
- Review — Check for consistency with brand voice, factual accuracy, and completeness.
- Deliver — Save to the appropriate output directory and update
schedule.mdif it is a scheduled piece.
Content Style Guide
- Blog posts: 1,500-3,000 words, well-structured with subheadings
- Social media posts: 100-300 words, conversational tone, include hashtags
- Marketing copy: concise and impactful, highlight key selling points, include a call to action (CTA)
Content Writing Template
When writing a blog post, follow this structure:
# [Title — clear, keyword-rich]
**TL;DR**: [1-2 sentence summary]
## Introduction
[Hook the reader, state the problem or opportunity]
## [Section 1 Heading]
[Key argument or insight, supported by data or examples]
## [Section 2 Heading]
...
## Conclusion / Next Steps
[Summarize takeaways, include CTA]
Data Briefing Template
When compiling a data briefing or operational report:
# [Period] Operations Briefing
## Highlights
- [Top 3 metrics or events worth noting]
## Key Metrics
| Metric | This Period | Previous Period | Change |
|--------------|-------------|-----------------|--------|
| ... | ... | ... | ... |
## Notable Events
- [Event with context and impact]
## Action Items
- [Recommended follow-ups based on the data]
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.
- 5d ago First seen · 82 lines · 67 tokens per session scan A 7a8d24a5d1aa
ops is a skill published in the GitHub repository 0xranx/golembot (320 stars, last pushed 17d ago), licensed MIT. It adds 67 tokens to every session and 611 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.
review-work
Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE…
visual-qa
MUST USE after building/changing any UI or when asked whether a page, component, or TUI looks right. Rigorous visual QA across web/page, terminal, and paginated-document surfaces. Prefer browser:control-in-app-browser for unauthenticated browser/page QA in Codex, then Playwright/agent-browser/dev-browser. Captures…
frontend
MUST USE for frontend/web UI/UX/visual work: building, styling, redesigning pages/components, React setup, performance audits, visual QA, taste, and polish. Routes four rulesets: design taste router and brand references; perfection for Playwright/Chromium Lighthouse/Core Web Vitals; ui-ux-db palettes/fonts/guidelines…
ulw-execute
Execute a Prometheus work plan with Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and Stop-hook continuation. Use after planning when the user says ulw-execute, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.