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 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/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/ops"><img src="https://agentmods.dev/badge/skills/0xranx/golembot/ops.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.00067 | $0.00611 |
| Opus 5.5 | $0.00027 | $0.00244 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 82 lines · 67 tokens per session scan A 7a8d24a5d1aa
ops is a skill published in the GitHub repository 0xranx/golembot (323 stars, last pushed 24d ago), licensed MIT. It adds 67 tokens to every session and 611 once invoked, about $0.0003 per session on Opus 5.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, or migrating its existing lint and format config onto Ultracite (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or…
ulw-execute
Executes a written ulw-plan 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.
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…